Software Product Cycle
STAGE 1 Initial Planning | STAGE 2 Planning Phase | |
---|---|---|
Order of Stage Activities | 1. The product owner should provide the business requirement document or given a template if required, after review by the PM, a PRD would be generated using the BRD, and a meeting would be set for review and approval by the management team. 2. Idea screening – for internal projects – by the product department 3. SWOT analysis – for internal projects – by the product department 4. Submission of finding for approval by the product manager | 1. Setting up the designated product team by the product manager. 2. Project Introduction to the team/Document sharing 3. Product Research |
Documents | Business Requirement Document | 1. Business requirement document (must be made available to the project team) 2. Product RACI matrix 3. Product requirement document (must be made available to the project team) |
Delivery TimeFrame | 2 working days for external projects and 5 working days for internal projects. NB: The difference in time is to allow the management to do a thorough research for internal projects while for external it is believed the product owner must have gone through that phase with their product team. | 3-5 Working Days |
Comments | Products that don’t meet up with our business requirement document standard will be rejected and sent back to the product owner. | |
Order of Approval | 1. The Director 2. Product manager | Product Manager |
STAGE 3 Requirement Gathering/Planning | STAGE 4 Design Phase/Analysis/Budgeting | |
---|---|---|
Order of Stage Activities | 1.Brainstorming session with the team 2.Project Approval for Internal Projects 3.MVP Scope agreement | 1. Product concept development 2. Product Budgeting 3. Design Phase 4. Milestone Breakdown 5. Design Reviews 6. Design approval from stakeholders |
Documents | 1. Project scope 2. Product specification document (must be made available to the project team) 3. Product marketing strategy (internal projects only) 4. Product value proposition chart (internal projects only) 5. Product idea validation – user survey (internal projects only) 6. Product beta and official launch plan document (internal projects only) 7. Competitive Analysis Documents (product unit) 8. Product Strategy and Vision Documents (product unit) 9. OKRs, KPIs, success metric document (product and project units | 1. Milestone documentation 2. Product designs and flows (must be made available to the project team) 3. Product Road Map 4.Risk and issue management 5. Work Breakdown Structure - can come in form of activities or sprint planning |
Delivery TimeFrame | 15 working days | 15 working days for first mile stone designs (Dependent on project) |
Comments | 1. For an external project, the budget will be approved within 2 working days after stage | 1. This timeframe includes the time the budget will be communicated to the product owner. 1. Changes on the product can only be done in this stage 2. The financial cost of any changes will be review and if it affects the working budget |
Order of Approval | 1. The Director 2. Product Manager | 1. Product Manager 2. CTO |
STAGE 5 Implementation Phase | STAGE 6 Development/Iteration Phase | |
---|---|---|
Order of Stage Activities | 1. Technical Setup 2. Sprint breakdown/Review 3. User Stories 4. Tasks Assigning | 1. Coding 2. Testing 3. Bug fix 4. Documentation 5. Continued Iteration |
Documents | 1. Technical document 2. Sprint Breakdown Documentation 3. Product Designer User story documentation | 1. Technical document 2. Minutes of meetings (project unit) 3. Weekly report (project unit) 4. Bi-Weekly retrospectives (project unit) 5. Reports for project and product teams review meeting (project unit) 6. Market requirement document (product unit - 3 working days) 7. Market strategy document (product unit - 3 working days) 8. Marketing plan document (product unit - 3 days) 9. Release notes (product unit - 3 days) 10. Feature scope document (product unit - 2 working days) 11. Feature request document (product unit - 1 working day) 12. Feature prioritization document (product unit - 1 working day) 13. Feature launch plan document (product unit - 2 working days) 14. Product guides and FAQs (product unit - internal projects only- 2 working days) 15. Terms of use (product unit - internal projects only- 2 working days) 16. Privacy policy (product unit - internal projects only- 2 working days) 17. Cookie policy (product unit - internal projects only - 2 working days) |
Delivery TimeFrame | 5 Days | Dependent on milestone |
Comments | 5 days to prepare for the first milestone other mile stone preparation will be done as the project continues | This phase is continue iteration and development phase |
Order of Approval | Product Manager | 1. Product Manager |
STAGE 7 Deployment | STAGE 8 Evaluation/ Closure | |
---|---|---|
Order of Stage Activities | 1. Usability Testing by end users/Stakeholders 2. Project will be reviewed by the The Director , project and program managers 3. Product alpha testing and debugging 4. Product beta testing and debugging 5. Approval for deployment | 1. Approval of the project deployment by the The Director in accordance with the documented specification. 2. Acceptance of the project by the product owner 3. Product market entry |
Documents | 1. Deployment Documentation | 1. Project retrospectives 2. Project closure document |
Delivery TimeFrame | ||
Comments | This phase is the preparation phase for go live | 1. At this stage, no changes will be approved. 2. If the project is internally owned, the changes will be effected on subsequent versions; however, if it is an external project, stage 4 processes will be applied. |
Order of Approval | The Director Product Manager | 1. Product Manager 2. Product owner 3. The Director |