Scrum: Events and Artifacts
Hello all,
Scrum is more than just a framework of Agile methodology of project management —it's a dynamic approach designed to handle complex problems and deliver value continuously.
Today, we’ll dive into the core components of Scrum: its events and artifacts. Let’s break down these Scrum components and explore how they can help you succeed with your project.
Scrum Events
Scrum events provide regular opportunities to inspect and adapt the artifacts, promoting transparency and improving the process. There is a breakdown of each event for you:
The Sprint
The Sprint is the container for all other events and represents a fixed length of one month or less. It is where ideas turn into value, and no changes are made that could endanger the Sprint Goal.
The entire Scrum Team (Product Owner, Scrum Master, and Developers) participates in the Sprint.
Meanwhile, only the Product Owner has the authority to cancel a Sprint. The decision to stop a Sprint can be made if the Sprint Goal becomes obsolete due to changes in business conditions or other significant factors.
Sprint Planning
This is where the magic begins. This event initiates the Sprint, laying out the work to be performed. It covers why the Sprint is valuable, what can be done, and how the chosen work will get done.
The Developers and Product Owner collaborate to set a Sprint Goal, choose Product Backlog items to tackle, and plan the work needed to deliver these items. The Product Owner ensures attendees are prepared and may invite others for advice. The Developers create the plan for the Sprint, and the Scrum Master ensures the event is effective.
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, this event is usually shorter in duration.
Daily Scrum
Often referred to as the Daily Standup, this 15-minute meeting is crucial for keeping the team aligned and focused. This event allows us to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
The Developers are the primary attendees. The Product Owner and Scrum Master may participate if actively working on Sprint Backlog items. It’s the Scrum Team’s opportunity to inspect progress, adapt plans, and address any roadblocks. By keeping this meeting short and focused, you ensure that your team stays agile and responsive throughout the Sprint.
The Daily Scrum is limited to 15 minutes and is held every working day of the Sprint.
Sprint Review
This is your chance to showcase the work completed and gather feedback. During the Sprint Review, the team presents the Increment to stakeholders, discussing what was accomplished and what needs adjustment. The goal of the meeting is to discuss progress toward the Product Goal with stakeholders.
The Scrum Team and key stakeholders are involved. It is a working session, not just a presentation.
Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint, with shorter durations for shorter Sprints.
Sprint Retrospective
The Retrospective is where reflection meets action. The Sprint Retrospective focuses on planning ways to increase quality and effectiveness. The Scrum Team reflects on the Sprint, discussing what went well, what didn’t, and how to improve.
The Scrum Team participates, discussing internal processes and potential improvements.
This event is timeboxed to a maximum of three hours for a one-month Sprint, and similarly shorter for shorter Sprints.
Scrum Artifacts
Scrum artifacts are tools that provide transparency and foster shared understanding. They are key to managing and delivering project work effectively. Here’s a breakdown of each artifact:
Product Backlog
Think of the Product Backlog as the master list of everything needed for the product.
This artifact is an ordered list of everything needed to improve the product. It evolves as new needs are discovered or priorities shift.
The Product Owner is accountable for the Product Backlog.
The Product Owner
The Product Goal serves as the commitment for the Product Backlog. It describes the future state of the product that serves as a target for the team to plan and work towards. The Product Goal provides focus and direction for the Product Backlog, ensuring that the items in the backlog align with this overarching objective.
Sprint Backlog
This artifact consists of the Sprint Goal and the Product Backlog items selected for the Sprint, along with the actionable plan for delivering the Increment. It’s a real-time view of what the team aims to achieve during the Sprint, providing clarity and focus.
The Developers are responsible for the Sprint Backlog.
The Sprint Goal represents the commitment for the Sprint Backlog. It outlines the single objective of the Sprint. It is formulated during Sprint Planning and represents what the Scrum Team aims to achieve in the upcoming Sprint. The Sprint Goal provides a cohesive focus for the team and guides their work throughout the Sprint. It ensures that the Sprint Backlog, which consists of selected Product Backlog items and a plan for delivering them, is aligned with this specific goal.
Increment
This artifact is the sum of all Product Backlog items completed during a Sprint and all previous Sprints. Each Increment builds on previous ones, adding value to the product. Ensuring that each Increment is thoroughly verified and usable is crucial for maintaining product quality and delivering value.
The Developers are also responsible for the Increment.
The Definition of Done is the commitment for the Increment. It is a formal description of the quality standards required for the Increment to be considered complete. It ensures that each Increment is usable and meets the agreed-upon criteria for quality and completeness. The Definition of Done provides transparency by defining what it means for work to be finished, allowing everyone to understand what is included in the Increment and ensuring consistency across the Scrum Team.
Integrating Events and Artifacts
Integrating Scrum's events and artifacts effectively into your project workflow is important for maximizing the benefits of the framework. Here is how you can proceed with this approach.
Start by focusing on the Product Backlog. Regularly updating the Product Backlog ensures that it reflects the current priorities and requirements. The Product Owner is primarily responsible for managing this artifact, which involves developing and communicating the Product Goal, creating and ordering Product Backlog items, and ensuring that the backlog remains transparent and understood by all team members.
During Sprint Planning, the Scrum Team selects items from the Product Backlog to create the Sprint Backlog. The Sprint Backlog includes the Sprint Goal, the selected Product Backlog items, and a plan for delivering the Increment. This plan must be detailed enough to allow the team to inspect their progress daily. The Sprint Goal, created during Sprint Planning, provides focus guiding the team on what they aim to achieve during the Sprint.
As the Sprint progresses, hold a Daily Scrum to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. This meeting helps the team adjust their plans based on new insights and emerging challenges, ensuring that they stay on track to meet the Sprint Goal.
At the end of the Sprint, conduct a Sprint Review to inspect the Increment and determine any necessary adaptations. During this event, the Scrum Team presents the results of their work to stakeholders and discusses what was accomplished and how it aligns with the Product Goal.
Finally, the Sprint Retrospective is an opportunity for the Scrum Team to inspect how the Sprint went in terms of processes, tools, and interactions. The team identifies what went well, what could be improved, and how to address any issues. The improvements identified in this event are then incorporated into the next Sprint, ensuring continuous enhancement of the team's practices and effectiveness.
Throughout these events, always ensure that each Increment meets the Definition of Done. This formal description defines the quality and completeness required for work to be considered part of the Increment.
I’m curious to hear about your experiences with Scrum. How have these events and artifacts impacted your projects? Share your insights and let’s continue the conversation!
Best, Olha