Scrum Events
Scrum is an empirical approach for managing work by allowing teams to inspect their progress and adapt their plans to reach a desired outcome, defined by 5 Events (Ceremonies).
In this article I will briefly examine every Scrum Event as from my point of view they are crucially important in Scrum.
You can see a visual representation of how the Scrum Events work together, below:
In this article I will briefly examine every Scrum Event as from my point of view they are crucially important in Scrum.
You can see a visual representation of how the Scrum Events work together, below:
Product Backlog Refinement
First event for the preparation of the next iteration, represents the act of adding new Product Backlog Items, Details, Estimates and Prioritization in the Product Backlog. It is an ongoing process in which the team together with the Product Owner collaborate on the details, refine and revise it.
It is the first step to work towards the product vision and the outcome of the refinement event is a prioritized list with Product Backlog items which are well understood by the team - called Product Backlog.
From my experience it is important to have a shared understanding about each item so that the team can estimate collaboratively using the Poker Planning technique and if needed to break-down the scope in smaller pieces to ensure that every item can be completed within one single sprint.
The prioritization of the Product Backlog items can be made by using multiple techniques - but MoSCoW techniques is frequently used.
From my experience it is important to have a shared understanding about each item so that the team can estimate collaboratively using the Poker Planning technique and if needed to break-down the scope in smaller pieces to ensure that every item can be completed within one single sprint.
The prioritization of the Product Backlog items can be made by using multiple techniques - but MoSCoW techniques is frequently used.
A good preparation of the Product Backlog Refinement event will lead to a smooth Sprint Planning.
Sprint Planning
Held in the first day of the sprint, the event focuses on the prioritized items required for delivery in the sprint and how these can be planned to be accomplished.
This event it usually contains 2 parts: discussion around what is required to be delivered in the sprint - the sprint goal, followed by the creation of tasks for each user stories and discussion in the team on how the product backlog items will be delivered as the team is self organized.
If the items requires new estimates during discussions, this can happen also during this session.
The Development Team, taking into consideration its Velocity, will forecast how much can be accomplished from the prioritized list and the outcome will be called Sprint Backlog - the team's commitment and focus in the current iteration
The sprint planning outcome is too have a Sprint Goal and a Sprint Backlog agreed by everyone to be realistic and achievable in one sprint.
For a good sprint delivery, the value, needs, risks, assumptions and other Definition of Ready criteria should be considered from planning, to ensure focus and to avoid surprises during the sprint.
Held in the first day of the sprint, the event focuses on the prioritized items required for delivery in the sprint and how these can be planned to be accomplished.
This event it usually contains 2 parts: discussion around what is required to be delivered in the sprint - the sprint goal, followed by the creation of tasks for each user stories and discussion in the team on how the product backlog items will be delivered as the team is self organized.
If the items requires new estimates during discussions, this can happen also during this session.
The Development Team, taking into consideration its Velocity, will forecast how much can be accomplished from the prioritized list and the outcome will be called Sprint Backlog - the team's commitment and focus in the current iteration
The sprint planning outcome is too have a Sprint Goal and a Sprint Backlog agreed by everyone to be realistic and achievable in one sprint.
For a good sprint delivery, the value, needs, risks, assumptions and other Definition of Ready criteria should be considered from planning, to ensure focus and to avoid surprises during the sprint.
Daily Scrum or Daily Stand-up
Reoccurring event which happens daily during the sprint - represents an opportunity for self-organisation, knowledge sharing, communication, just-in-time planning and raising any risks, impediments or changes that may occur.
Happens at the same time, at the same hour and it is time-boxed to 15 mins. In order to keep focus people are standing up.
The event is an inspect and adapt session towards sprint progress, paying attention to the Definition of Done checklist.
To be efficient there are 3 questions that are used for sharing sprint progress by each team member:
- What did I accomplished for the sprint from the last Stand-up ?
- What I plan to do until the next Stand-up to support the Sprint Goal?
- What issues are impeding my way?
Being a time-boxed meeting and to not lose focus, it is important to take any development, questions, side discussions after the event.
Reoccurring event which happens daily during the sprint - represents an opportunity for self-organisation, knowledge sharing, communication, just-in-time planning and raising any risks, impediments or changes that may occur.
Happens at the same time, at the same hour and it is time-boxed to 15 mins. In order to keep focus people are standing up.
The event is an inspect and adapt session towards sprint progress, paying attention to the Definition of Done checklist.
To be efficient there are 3 questions that are used for sharing sprint progress by each team member:
- What did I accomplished for the sprint from the last Stand-up ?
- What I plan to do until the next Stand-up to support the Sprint Goal?
- What issues are impeding my way?
Being a time-boxed meeting and to not lose focus, it is important to take any development, questions, side discussions after the event.
Sprint Review
At the end of the sprint, the team members inspect and adapt how far they get with their product, from a work perspective.
The team presents to the stakeholders a Demo with the product increment accomplished at the end of the sprint.
During this session, feedback is gathered so that the team will know what needs to be adjusted in the future to meet customer's needs.
Feedback can be translated into new items to be discussed in the next Product Backlog Refinement event or in the next Sprint Planning event, if has a higher priority.
At the end of the sprint, the team members inspect and adapt how far they get with their product, from a work perspective.
The team presents to the stakeholders a Demo with the product increment accomplished at the end of the sprint.
During this session, feedback is gathered so that the team will know what needs to be adjusted in the future to meet customer's needs.
Feedback can be translated into new items to be discussed in the next Product Backlog Refinement event or in the next Sprint Planning event, if has a higher priority.
Sprint Retrospective
Marks the end of the sprint, being the event in which the team members inspect how they organized themselves during the sprint to adapt in the next sprint.
The entire Scrum team should participate in the retrospective to share leanings and failures with regards to people, relationships, processes and tools.
The outcome will be a list of top actions which can be taken by the team to make things better next time.
From my experience, the environment should be Safe enough so that everyone is open to address what could be improved in terms of processes - as a learning from the last sprint.
Empirical approach, Scrum is based on Transparency, Inspection and Adaptation (so called Scrum 3 Pillars) that are reflected in every Scrum Event, so the attitude of each team member should be towards continuous improvement and transparency.
Marks the end of the sprint, being the event in which the team members inspect how they organized themselves during the sprint to adapt in the next sprint.
The entire Scrum team should participate in the retrospective to share leanings and failures with regards to people, relationships, processes and tools.
The outcome will be a list of top actions which can be taken by the team to make things better next time.
From my experience, the environment should be Safe enough so that everyone is open to address what could be improved in terms of processes - as a learning from the last sprint.
Empirical approach, Scrum is based on Transparency, Inspection and Adaptation (so called Scrum 3 Pillars) that are reflected in every Scrum Event, so the attitude of each team member should be towards continuous improvement and transparency.
Comments
Post a Comment
Please leave a comment below