As promised in my last post, I will be discussing about ‘Scrum Ceremonies and Artifacts’ in this post.
Scrum Ceremonies:There are following ceremonies in Scrum:
- Sprint Planning Meeting
- Daily Scrum Meeting
- Sprint Review/Demonstration Meeting
- Sprint Retrospection Meeting
Sprint Planning Meeting :
Time box: 4 hours (2 weeks sprint) / 8 hours (4 weeks sprint)
Attendees: Scrum Master, Product Owner and Scrum Team
This meeting consists of 2 parts:
“What” is to be developed?: In first part Product owner describes and presents the ordered Product Backlog items and Sprint goal to the entire Scrum Team, who collaborates about understanding the work of the Sprint.
“How” it will deliver the Sprint Goal?: In second half of this meeting scrum team plans in detail which tasks are necessary to fulfill the Sprint Goal and deliver the forecasted Product Backlog items according to capacity of team.
Inputs to Sprint Planning Meeting: Product Backlog and Team Capacity
Output of Sprint Planning Meeting: Sprint Backlog and Sprint Goal
Daily Scrum Meeting: The Daily Scrum is the key inspect and adapt meeting during a Sprint.During the Sprint execution , the scrum Team meets every day, for Daily Scrum meeting and inspects the progress and ensures communication flow inside the Team.It is a short (15 minutes) meeting.
Time box: 15 Minutes
Attendees: Scrum Master, Product Owner(Optional) and Scrum Team
It is held at the same time at same place each day.During the meeting, each Team member explains:
- What have I accomplished since the last meeting?
- What am I going to do before the next meeting?
- What obstacles are in my way?
The Daily Scrum improves communication, eliminates other meetings, identifies & removes impediments to development, highlights and promotes quick decision-making, and improves everyone’s level of project knowledge.The responsibility for conducting the Daily Scrum is with the Team and Scrum Master facilitates the same.The Scrum Master ensures the all the impediments are noted and he/she will get these resolved. He coaches the Team to keep the Daily Scrum short and making sure that people speak briefly.
Sprint Review/Demonstration Meeting:
Time box: 1.5 hours (2 weeks sprint) / 3 hours (4 weeks sprint)
Attendees: Scrum Master, Product Owner and Scrum Team, All the Stakeholder/Sponsors, Customers.
A Sprint Review/Demo meeting is held at the end of the Sprint to inspect the Increment. The Team demonstrates the Increment with focus on the Sprint Goal according to the Definition of Done. The Product Owner reviews and accepts the delivered Increment.During the Sprint Review, Product Owner,Team and stakeholders review what was done. This meeting should not have Slides, with the presentation of the results but should have working demonstration of the work planned in sprint planning.
After the demonstration the Product Owner and other relevant stakeholders tell their impressions and clarify their requirements (user stories) if a requirement was not implement right. The Product Owner identifies what has been done and what hasn’t been done (according to the Definition of Done). The Product Owner accepts the user stories that have been done. Results of this meeting can be new requirements in the Product Backlog, and a new prioritization of existing Product Backlog items.
Sprint Retrospection Meeting:
Time box: 2 hours (2 weeks sprint) / 4 hours (4 weeks sprint)
Attendees: Scrum Master, Product Owner and Scrum Team
In the Sprint Retrospective the Scrum Team revises their way of work in the past in order to make it more efficient and effective in the future. The Scrum Master encourages the Scrum Team to search for best practices and to identify improvement measures that it will implement in the next Sprint. After the Sprint Review and before the next Sprint Planning , the Team has a Sprint Retrospective.
Whereas the Sprint Review is about the product, the Sprint Retrospective is about the process – the way in which the Scrum team works. It is never omitted.
In the Sprint Retrospective meeting, the Scrum Master encourages the Development Team to inspect, within the Scrum framework and practices, how the last Sprint went in regards to people, relationships, process and tools. The Team should identify and prioritize the major items that went well, and those items that, if done differently, could make things even better. By the end of the Sprint Retrospective, the Team should have identified actionable improvement measures that they will implement in the next Sprint.
Scrum Artifacts:There are following artifacts in Scrum:
- Product Backlog
- Sprint Backlog
- Product Increment
Product Backlog :
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.It contains broad descriptions of all required features, functions, enhancements, wish-list items, etc. The Product Backlog defines the “What” that will be built.
The Product Backlog is the property of the Product Owner. He is responsible for its content, its availability and prioritization. Business value is set by the Product Owner. Development effort is set by the Team.All items in the Product Backlog are prioritized and sorted by business value. The top priority items drive the next development activities. Higher priority items are clearer and have more detailed information than lower priority items. As Increments are being reviewed and releases of the product are being used, feedback is provided and the Product Backlog emerges into a larger, more exhaustive and more detailed list.
The Product Backlog items are initially established and calculated during Release Planning. Afterwards they are updated in Sprint Planning or Backlog Groomings. The top priority items are selected for development during Sprint Planning developed in the Sprint and reviewed in the Sprint Review.
Sprint Backlog :
The Sprint Backlog is the set of Product Backlog items selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Team in sprint planning meeting and is about what functionality will be in the next Increment and the work needed to deliver that functionality.
In the Sprint Backlog the Team plans the necessary tasks to implement the items selected from the Product Backlog in Sprint Planning . The Sprint Backlog is property of the Team. Estimations are set by the Development Team.The Team keeps the Sprint Backlog always up to date during the Sprint. As the work is done, the Development Team may find that more, less or different tasks are needed.The Sprint Burn Down graph shows the remaining effort across the time of a Sprint.Often a Task Board is used to see and change the state of the tasks of the current sprint, like “to do”, “in progress” and “done”.
At the end of a Sprint the new Increment must be in a usable condition and meet the Scrum Team’s Definition of Done.In Scrum, the Development Team delivers each Sprint an Increment. The increment must consist of thoroughly tested code that has been built into an executable, and the user operation of the functionality is documented either in Help files or user documentation. These requirements are documented in the Definition of Done.If everything works fine and the Development Team has estimated well, the Increment includes all items, which were planned in the Sprint Backlog, tested and documented.