Sprint review purpose – A sprint review is more than just a demo session held to provide a routine status update. The main purpose of a sprint review is to inspect the outcome of the sprint, collect feedback from all the stakeholders, and adapt the backlog going forward. When done right, a sprint review can help you create transparency, foster collaboration, and generate valuable insights.
What is the main purpose of a sprint planning meeting?
What is sprint planning? – Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team.
In scrum, the sprint is a set period of time where all the work is done. However, before you can leap into action you have to set up the sprint. You need to decide on how long the time box is going to be, the sprint goal, and where you’re going to start. The sprint planning session kicks off the sprint by setting the agenda and focus.
If done correctly, it also creates an environment where the team is motivated, challenged, and can be successful. Bad sprint plans can derail the team by setting unrealistic expectations.
The What – The product owner describes the objective(or goal) of the sprint and what backlog items contribute to that goal. The scrum team decides what can be done in the coming sprint and what they will do during the sprint to make that happen. The How – The development team plans the work necessary to deliver the sprint goal. Ultimately, the resulting sprint plan is a negotiation between the development team and product owner based on value and effort. The Who – You cannot do sprint planning without the product owner or the development team. The product owner defines the goal based on the value that they seek. The development team needs to understand how they can or cannot deliver that goal. If either is missing from this event it makes planning the sprint almost impossible. The Inputs – A great starting point for the sprint plan is the product backlog as it provides a list of ‘stuff’ that could potentially be part of the current sprint. The team should also look at the existing work done in the increment and have a view to capacity. The Outputs – The most important outcome for the sprint planning meeting is that the team can describe the goal of the sprint and how it will start working toward that goal. This is made visible in the sprint backlog.
What is a sprint review in agile?
What is a sprint review meeting? – In Agile project management, a sprint review is an informal meeting held at the end of a sprint, in which the Scrum team shows what was accomplished during this period. This typically takes the form of a demonstration of new features, with the goal of creating transparency, fostering collaboration, and generating feedback.
- The purpose of a Scrum sprint review is not to provide a status update or make a presentation to stakeholders; it is to collect and absorb feedback on the actual product increment—which is the sum of all backlog items completed during the sprint.
- If needed, the sprint review group will adapt the backlog going forward, in order to maximize efficiency in sprints to come.
Guide: Agile Marketing Cheat Sheet Guide: The Complete Guide to Agile Marketing
Who does the demo in sprint review?
#8. Who leads the Sprint Review? – The Scrum Master facilitates the Sprint Review, and the demo is done by the Product Owner, mainly. But the team member should have the opportunity to demo as well.
What is the main agenda for sprint planning meeting?
Confirm the team’s capacity. Identify any availability factors that could affect your team’s capacity, like additional workloads, technology availability, member skills or team changes. Work to determine accurate story point measurements and velocity determinations for your sprint. Propose product backlog items.