Scrum defines several events (sometimes called ceremonies) that occur inside and outside each sprint:
1) Product Backlog Grooming:
Backlog grooming is the only ceremony in scrum that doesn’t have a defined time box or even a frequency.
It is, however, a critical responsibility of the product owner with the help of their team to add new items to the list and order them based on their priority.
At the same time, outdated, redundant or non-valuable items should be removed from the backlog to keep it clean, valuable and actionable.
We call this as Release plan meeting happens quarterly once.
Action taken from grooming meeting:
1) Estimate user stories
2) Insert new user stories
3) Re-Prioritize user stories
4) Refine user stories
5) Remove user stories
2) Sprint Planning:
A sprint planning meeting is when the team (including the Scrum Master, Scrum Product Manager, and Scrum Team) meets to determine which backlog items will be handled in the next sprint.
The sprint planning Scrum ceremony is a collaborative process that allows team members to have a say in when work happens.
3) Daily Scrum:
During this meeting, each team member should briefly provide the answers of the following three questions:
1) What has he/she accomplished since the last daily Scrum meeting?
2) What is he/she is going to accomplish until the next Scrum meeting?
3) What are the impediments that prevent him/her from accomplishing his/her tasks?
4) Sprint Review:
Sprint reviews focus on the product being developed, specifically on the potentially shippable product increment created during the sprint.
During a sprint review, the scrum team invites stakeholders to discuss what was completed during the sprint.
They adapt the product backlog as needed based on this feedback. The product owner has the option to release any of the completed functionality.
Though a demo might be part of this meeting, the primary purpose of the sprint review is the inspect and adapt capability provided by the discussion.
5) Sprint Retrospective:
The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss
1) what went well during the previous sprint cycle?
2) what went wrong during the previous sprint cycle?
3) what can be improved for the next sprint?
The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects.
Comments
Post a Comment