Skip to content
← Click here to get started. A few notable definitions.💎 Epics - Product planning often starts with teams identify larger initiatives, or epics.✅ Issues / tasks - Actionable items, called “issues,” are added to epics so more granular tasks can be assigned to specific owners.👩🏻💻 User stories - Features and functionalities stated from the perspective of the user/customer—their goals and their expectations of the product.🗓 Timeline - A clear view of when epics and issues are due to avoid deadlines from slipping, and help mitigate any blockers that may arise. You can update dates/times directly on the Timeline by dragging the bars directly on timeline. How to use this templateIf you use Jira to track issues.
A service which listens to updates on the Coda survey form and creates a state machine JSON representation, which is stored in a DynamoDB
Shahil PoonsamyShahil Poonsamy
Shahil PoonsamyEnsuring the sign-up flow is bug free and can scale to add more features for respondents’Shahil Poonsamy
Shahil Poonsamy
Shahil Poonsamy
Shahil Poonsamy
Shahil Poonsamy
More
Share
Explore
Epics and issues
Create a hierarchy of tasks for your team.
Help your team focus by breaking down larger initiatives into smaller tasks with clear deadlines.
To keep product launches on track, many teams rely on tools that help them manage the following:
This template lets you do all of the above in the same document and uses , which make it easy to add Coda building blocks, embed images, comment, and collaborate—all from inside a cell. This means you won’t need to switch to a separate page or doc to start writing.
1. Make a copy of this doc for you and your team. You only need to do this once a quarter or year, depending on your product cycles.
Copy doc
2. Clear all the sample data.
Clear all sample data
3. Head to the page to personalize this doc.
Customizations_sukC8
You can pull in and sync your data to Coda instead so you can visualize progress and tie issues to your project strategy write-ups, all in the same doc. Try that comes with a Jira integration built-in.
Timeline view
Not configured
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Sep 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Oct 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Nov 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Dec 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Jan 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Feb 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
Mar 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Apr 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
May 2026
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Task 1
Task 2
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Month
TodayFit
Epics
Add new epic
Automation Backend
Description
Overview
This Epic encapsulates the creation of a serverless backend to use with automating the landbot. There are two main services which are required:
Key Owner
Testing Pipeline
Description
Overview
This Epic details the implementation of a testing pipeline to fit in with our automated services, as well as some manual processes.
Business motivation
Key Owner
Data Cleaning
Description
Overview
The goal of this epic is to achieve an automated data cleaning pipeline, between process that interact with the central SQL database and of data that is already within the database. Besides just data type and value correctness, this cleaning refers to the validation of data that respondents’ have provided as their survey answers, and both identifying and handling cases where invalid or fraudulent data has been provided.
Key Owner
Landbot V2
Description
Overview
The Landbot flows need to be cleaned up in order to ensure compatibility and functionality with new services. This epic describes the steps taken to achieve a landbot flow(s) which is fully automated and requires no intervention between surveys. In particular, this focuses on:
Key Owner
Database Restructuring
Description
Overview
This epic describes the tasks to restructure the SQL database in a way that can be best utilized by all the other systems, as well as implementing that integration and providing backup systems while restructuring occurs
Key Owner
Data Visualisation Template
Description
Overview
The ultimate goal for data visualisation is to be able to fully automate it using machine learning, with insights gained from data provided by respondents and their answer history. However, the most short term gains can be achieved by simplifying a data visualisation template that can reduce the hours needed to construct a report for a client. With a restructuring of the database, this can be integrated.
Key Owner
Monitoring
Description
Overview
Though not mission critical, the stories in this epic all contribute towards a goal of gaining insight into the performance of the business systems. This includes metrics surrounding latency of chatbots, the lead time between ideas and implementation, and other means of identifying performance. At the very least, basic alerts should be created early on to determine failure of key systems. This is ongoing and should be implemented as new features are added
Key Owner
Frontend Redesign
Description
Overview
In order to make an effortless self-service website for our clients, we need to redesign our existing frontend form-builder to provide more utility. This includes redesigning the form builder in coda, or moving it to retool entirely, as well as extending the front end with a web page that allows for user account creation and monitoring of survey process
Key Owner
Issues
Filter issue by quarter:
Q2
+1Add new issue
Quarter
Epic
Issues
Details
Start
Duration
Team(s)
Effort
Q2
Automation Backend
Create Lambda to retrieve survey from front end API
When Manually triggered ,
12 hrs
Backend
Core
Small
Add automatic triggering of Lambda
When button pressed on Coda ,
12 hrs
Backend
Core
Small
Extend Lambda to convert coda API data to state machine JSON
When Lambda receives survey information from API gateway,
1 day 8 hrs
Backend
Core
Medium
Implement DynamoDB for JSON storage
When A DynamoDB instance is queried on a Survey ID ,
16 hrs
Backend
Core
Medium
Create Lambda service to retrieve JSON from DynamoDB when triggered
When manually triggered ,
16 hrs
Backend
Core
Small
Extend Lambda to return a state from JSON when executed with a current-state context
When this lambda is executed with a hard-coded current state (for tests) ,
1 day 8 hrs
Backend
Core
Medium
Attach API gateway to Lambdas
Attach API gateways to the Lambdas in order to communicate with Landbot.
16 hrs
Backend
Small
Modify existing/create new Lambda service which receives data from Landbot and stores it in SQL database
Lambda should receive data from API call and link to a SQL database server to perform queries
16 hrs
Backend
Small
6 days 8 hrs
Sum
Monitoring
Implement monitoring of Lambda triggers
When the Lambda service is executed ,
6 hrs
Backend
User Experience
Small
Implement monitoring in API code according to delta standards
When exceptions are thrown ,
12 hrs
Backend
User Experience
Small
Add metrics to monitor in Landbot
Tracking of determined metrics to monitor the health of Landbot. This can’t be easily done within landbot, so a third party software could be used or a separate flow
20 hrs
Backend
User Experience
Medium
1 day 14 hrs
Sum
Landbot V2
Create a development environment in Landbot to test new bots
Set up a new bot flow that can be used for testing. Includes creating an appropriate development channel and number list to test bots securely, without impacting any users in production.
6 hrs
Core
Backend
Small
Create a generic bot flow with webhooks that query the Lambda service for survey questions
When the bot begins its flow ,
1 day 16 hrs
Core
Backend
Large
Redesign the signup flow to streamline and debug the process
The current sign up flow has too many bugs and there are many branches. These branches should be streamlined to reduce redundancy and questions/logic should be implemented to prevent bad data from being input
16 hrs
Backend
User Experience
Medium
Extend bot flow to send data to Lambda service for DB storage via API call
Webhooks should be implemented in Landbot flow to send the stored variables to a Lambda service using API endpoints. The Lambda service is responsible for inserting/updating the SQL Database
8 hrs
Backend
Core
Small
2 days 22 hrs
Sum
Database Restructuring
Identify current database issues
Our database is currently not being updated with the right data, we need to identify what is causing this
8 hrs
Backend
Small
Investigate existing database schema
The database schema needs to be investigated to determine if it will meet the needs of the proposed business plan, and if changes need to be made to accommodate it.
8 hrs
Backend
Small
Debug Database or Migrate to new schema
Depending on the nature of the bugs, migrating to a new schema might fix them.
16 hrs
Backend
Medium
1 day 8 hrs
Sum
Testing Pipeline
Set up development environments for Lambdas
Create different staging environments for Lambda code to allow for integration/smoke screen tests at each layer. DevOps and Cheslyn in particular can assist with this
16 hrs
Backend
Small
Implement Endpoint Testing on Lambdas
Lambdas should have their inputs and expected outputs mapped at a high level and the QA team can construct test cases for them, which should be used to validate their functionality
1 day
Backend
Medium
1 day 16 hrs
Sum
Frontend Redesign
Standardize survey question format
In order to accommodate the automation backend, the question format of surveys needs to be standardized. This will allow for flexibility in moving between front end software as long as the API calls to the back end service are made in the same format.
8 hrs
User Experience
Core
Backend
Small
8 hrs
Sum
Data Visualisation Template
Onboard onto Tableu
Data Studio is proving too slow to work with, so the first step in improving the data visualisation speed is onboarding onto Tableu - a more extensive platform that should increase the time it takes to create a report - before creating a standardized template
8 hrs
Core
Small
8 hrs
Sum
Data Cleaning
Implement data cleaning pipeline
Survey data should be cleaned before being inserted into database
1 day 8 hrs
Backend
Core
Medium
1 day 8 hrs
Sum
15 days 20 hrs
Sum
Release Milestones
Survey Form to Landbot Flow Automation
This release will see the backend automation structure and functionality implemented in order to coordinate the generic Landbot flow (Landbot V2), which will then also have a front-end survey form builder in place to provide a client with a one-click creation of a survey that is automatically sent out to participants and have their responses recorded.
Data Pipelines and Cleaning
This release will revolve around the treating and handling of data all parts of the overall system to ensure that is is appropriately cleaned and handled to reduce time and errors. While the survey automation release will focus on the back end and the process up until the survey has been delivered to participants, this release will focus more on the processes after they have responded and how their data is handled.
Data Visualisation and UX
This milestone contains the reworking of our data visualisation process to reduce the time it takes to generate a report for a client, as well as implementing other front end systems to increase the quality of a client’s experience with the service.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.