Cover Page
Sprint Phases
1. Product Backlog
The product backlog is the list of functionalities with the short descriptions derived from the requirements and the roadmap of the project; and they are displayed in terms of user stories. Product backlog is the single source of requirements for any changes to be made to the end product. User stories are prioritized by the product owner in discussion with the development team considering the business priority of those user stories and the dependencies on the other stories, if any. Responsibility of managing the product backlog lies with the product owner.
2. Sprint Planning
Sprint planning meeting is attended by the product owner, ScrumMaster, and the development team.
Sprint planning meeting will last the length based on the following rule of thumb: ‘Multiply the number of weeks in your sprint by 2 hours’ and this defines the duration of the sprint planning.
How and when it will be decided what should be the duration of the sprint and into how many sprints the project be divided into to address the requirements in the product backlog.
What is ‘Sprint 0’?
Sprint 0 is the phase wherein the resource planning, project planning, sprint duration, and the number of sprints will be decided and also a bit more discussion happens on the product backlog items.
Sprint planning is divided into 2 parts:
- Sprint Goal
- Sprint Backlog
Sprint Goal
The first half of sprint planning goes with deciding the sprint goal. Here the team discusses on what needs to be achieved at the end of that particular sprint. It is discussed and decided collaboratively by the team and the product owner. Sprint goal can be used for quick reporting on what has been decided to complete as part of that sprint to the interested stakeholders who are keen to know what is happening.
Sprint Backlog
This is the other output of sprint planning. The Sprint backlog is the list of the product backlog item for which the development team commits to deliver as part of that particular sprint.
Sprint Velocity
Sprint velocity is the capability of the development team to deliver the number of user stories based on the estimated story points. Sprint velocity of the first sprint decides the capacity of the development team and hence will be useful for planning further sprints accordingly.
3. Sprint Backlog
Sprint Backlog is the list of the product backlog item for which the Development team commits to deliver as part of that particular sprint.
4. Sprint
Defined period of time in which the specific committed work has to be completed. Sprint is timeboxed and cannot be extended under any circumstance, irrespective of whether all the user stories committed are delivered or not. If any user story or part of a user story is pending after the sprint completion time, that particular user story will be moved back to the product backlog for reprioritization.