| A | B | C | D | E | F | ||
|---|---|---|---|---|---|---|---|
1 | Purpose Conveys the scope of various tasks that need to be coordinated to build and launch the product/feature | What is the task? Based on the purpose, select the appropriate from the drop-down | Who is the task owner? Does the following to finish task: 1. Schedule and run meetings 2. Gather feedback and share updates 3. Follow-up with stakeholders | Whose involvement is needed to accomplish the task ? Please select one from the drop-down list of your identified stakeholders | What is their role? Select the stakeholder's role from the drop-down. Note: 'Scrum Team' role is applicable to stakeholder 'Scrum Team' only | By when, does the task need to be completed? Select milestone keeping in mind nature of the task,downstream effects of delaying task | |
2 | Evangelize internally | Setup PRD review meeting to receive feedback | Product Manager | Head of Product | Approver (Has the final say on a specific aspect of the project) | Set a target week | |
3 | Impacted Product Managers | Contributors (Consulted for their opinions or expertise to help with project decisions) | |||||
4 | Setup meeting to share MVP scope and walk-through design to gather feedback | Cross-functional Stakeholders | Contributors (Consulted for their opinions or expertise to help with project decisions) | ||||
5 | Setup meeting to kickoff project with the scrum team | Scrum Team | Scrum Team (Involved directly in product development efforts) | ||||
6 | Involve legal and compliance | Setup meeting to review MVP scope and identify possible legal updates.e.g Terms of Use and Privacy Policy | Product Manager | Legal and Compliance | Contributors (Consulted for their opinions or expertise to help with project decisions) | Set a target week | |
7 | Get feedback on previously identified legal areas to update. e.g Terms of Use and Privacy Policy | Legal and Compliance | Contributors (Consulted for their opinions or expertise to help with project decisions) | Before project's final sprint starts | |||
8 | Incorporate stakeholders feedback | Discuss the prioritized feedback received from stakeholders to update scope and design | Product Manager | Product Designer | Scrum Team (Involved directly in product development efforts) | Before project's sprint 0 starts | |
9 | Initiate and maintain feedback loop | Create a project-specific communication channel (in Slack etc) to share insights from customer meetings/usability tests/data analysis | Product Manager | All except Legal and Compliance | Contributors (Consulted for their opinions or expertise to help with project decisions) | Ongoing activity | |
10 | Plan development work | Setup solution feasibility discussions to understand the work involved/identify inter-dependencies and potential risks | Product Manager | Scrum Team | Scrum Team (Involved directly in product development efforts) | Before project's sprint 0 starts | |
11 | Identify critical spike and engineering design work to complete prior to product/feature development | Engineering Lead | |||||
12 | Manage product/feature testing | Share and review the project's test strategy | QA | Scrum Team | Scrum Team (Involved directly in product development efforts) | Before project's sprint 1 starts | |
13 | Setup analytics tracking | Review analytics tracking requirements | Data Analyst | Scrum Team | Scrum Team (Involved directly in product development efforts) | Before project's sprint 1 starts | |
14 | Prepare for every sprint | Create tickets for each sprint based on the test strategy | QA | Scrum Team | Scrum Team (Involved directly in product development efforts) | Before each sprint starts | |
15 | Create tickets for each sprint based on the analytics tracking requirements | Data Analyst | |||||
16 | Finalize user-stories and design to add for each sprint | Product Manager | |||||
17 | Coordinate product/feature launch | Discuss launch plan and targeted timelines to align with development cycle | Product Marketing | Product Manager | Contributors (Consulted for their opinions or expertise to help with project decisions) | Before project's sprint 1 starts | |
18 | Identify the support material that needs to be prepared and targeted timelines to align with development cycle | Customer Service | Product Manager | Contributors (Consulted for their opinions or expertise to help with project decisions) | Before project's sprint 1 starts | ||
19 | Communicate project progress | Share project's progress and highlight any risks (setup recurring meeting/send email/ share via team's channel e.g Slack) | Product Manager | Head of Product/Impacted Product Managers/Cross-functional stakeholders | Informed (No authority over the decisions and need to stay updated on the progress since it impacts their own work) | Before each sprint ends | |
20 | Receive product/feature sign-off | Setup meeting to demo the feature and conduct end-to-end feature testing to identify bugs and receive feedback | Product Manager | Head of Product | Approver (Has the final say on a specific aspect of the project) | Before project's last sprint ends | |
21 | Impacted Product Managers | Contributors (Consulted for their opinions or expertise to help with project decisions) | |||||
22 | Cross-functional Stakeholders | Informed (No authority over the decisions and need to stay updated on the progress since it impacts their own work) |