Planning a Version
- Akshay Aggarwal (Unlicensed)
What is the purpose of the Article?
You will understand what is a Version in Eshopbox
You will understand how a Version is planned
Audience
Product Managers
Software Development Engineers
Planning a Version
You will decide the stakeholders required for only Version planning meeting
Plan the Version for the coming month on the basis of business goals for the month on the 29th of the previous month.
The PM and SDE-II are required to come prepared with a rough draft of the goals for the month in the meeting. These goal will form the base of discussion in the meeting.
The document will consist of business goals, goal priority, requirements, dependencies and resources in a tabular format which can be later used to create Epics.
Document the Version plan document in the Confluence space of your project
You will share the Version plan document with all project members on e-mail
Format of Version Plan document
Goals | Priority | Dependencies | Stakeholder | Done | Pending | Hours | Status |
|---|---|---|---|---|---|---|---|
Capillary Implementation ( Blackberrys ) | P1 | backend | Anup |
|
| Planning - 32 coding - 40 Testing -40 | Pending |
PWA ( Platform Feature as a Stand-alone ) | P2 | frontend & backend | Manas | backend |
| Planning - 16 Coding - 24 Testing - 24 | In Progress |
Shopify out of stock | P1 | backend | Ajay/Prateek | backend | UI | Coding - 16 Testing 16 | Done |
Priority: You will decide the priority of the goal which will determine the order and time this goal should be taken up in the month(Scale: P1/Highest, P2/High, P3/Medium, P4/Low, P5/Lowest)
Goal: Is the goal that the team needs to achieve by the month end. The goals can be any new functionality or an improvement on the existing ones that would benefit the company and its clients.
Example: Capillary Integration, Managing Returns etc
Dependencies: Whether the Frontend, Backend or both teams would be involved in this goal
Stakeholder: The developers that will be working to achieve this goal
Done: Which aspect of the Goal is completed. For example if both frontend & backend is involved then you need to mention in this column if either backend or frontend is complete
Pending: Which aspect of the Goal is pending. For example: UI
Hours: No of hours required to completed the Goal
Planning: No of hours for planning of the Goal
Coding: No of hours required for completing the coding
Testing: No of hours required for completing the testing
Status: Is the Goal completed, is in in-progress state or pending to be taken up
Glossary
PM: Project Manager
SDE: Software Development Engineer