When a product is already in the market and we take over, we first try to understand what has been built so far. This is done by making a matrix of users and features. Each feature is then broken down to sub-feature level to understand dependencies. Any product roadmap developed by then is understood along with development governance that has been put in place.
In other words, taking over the application midway does not mean that the application development needs to stop. It just means that we try to take over the application management as soon as possible before we get involved in Product Management.
Depending on the size of the project, it can take us anywhere from 4-8 weeks to start Product Management for applications that are already in production.
| Activity | Deliverable | Duration |
|---|---|---|
| Capture the idea of what is to developed and the opportunity being tapped |
Executive Summary | 2 weeks |
| Activity | Deliverable(s) | Duration |
|---|---|---|
| Capture Business Requirements | Business Requirements Document (BRD) | 3-4 weeks |
| Make a list of modules for the product | User – Module Matrix | |
| Define minimum features that need to be built for the soft launch |
Minimum Viable Product | 1 Week |
| Define how development & delivery will be managed |
Project Governance | 1 Week |
| Activity | Deliverable(s) | Duration |
|---|---|---|
| One line user stories for MVP | User Stories | 2 weeks |
| Define 2 more Product Features for the application |
Product Roadmap (MVP + 2 Releases) | 2 weeks |
| User Story Grooming for the Sprint | Sprint Plan | 1 Week |
| Define how application will be validated | Application Validation Plan | 2 Week |