Familiarity with Scrum events and artifacts is essential for guiding the Scrum Team’s work and keeping workflows transparent and adaptable. This section covers the main events - Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective - and key artifacts: Product Backlog, Sprint Backlog, and Increment. At Wunder, we use Scrum as our project delivery foundation, adapting it over time. Here, however, we’re focusing on Scrum’s core elements to ensure the basics are well understood before introducing our tailored approach.
The Scrum framework organizes work into events designed to ensure transparency, inspection, and adaptation. Each event involves key Scrum artifacts, which track progress and align priorities with project goals. In this article, we will cover the five main Scrum events - Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective - highlighting the role of each artifact within them: the Product Backlog, Sprint Backlog, and Increment. For a deeper understanding of the Scrum process and terminology, please check the articles Scrum in a nutshell and Scrum roles and responsibilities.
Each event and artifact has a specific role in maintaining focus, aligning priorities, and promoting continuous improvement. Together, they provide a structured, iterative approach to delivering value, enabling the Team to respond to new information while staying aligned with project goals. Let's explore them in detail.
The Sprint
The Sprint is a time-boxed iteration, usually lasting from one to four weeks, during which the Scrum Team works toward a potentially shippable Increment of the product. The Sprint sets a consistent rhythm, providing clear start and end points for planning, execution, review, and adaptation. During the Sprint, the Scrum Team works exclusively on items from the Sprint Backlog, which are selected and refined during Sprint Planning. The Product Backlog and Sprint Backlog guide the Team’s daily work, ensuring focus on delivering the Sprint Goal. Once a Sprint begins, no changes are made that would threaten the Sprint Goal, keeping the Team concentrated on completing their committed work.
Sprint Planning
Sprint Planning initiates each Sprint and sets the scope and objectives. The Product Owner leads this session by presenting the Product Backlog, a prioritized list of user stories representing project requirements. During Sprint Planning, the Team selects the highest-priority stories that align with the Sprint Goal, placing these into the Sprint Backlog.
The Sprint Backlog becomes the Team’s focus for the Sprint, detailing both the user stories selected and the tasks needed to complete each one. By limiting planning to just one Sprint, the Team benefits from having the latest project insights and user feedback, enabling decisions based on current needs rather than assumptions. With these priorities set, the Sprint begins.
Daily Scrum
The Daily Scrum is a brief, 15-minute meeting held each day of the Sprint. The goal of this meeting is to keep the Team aligned on their daily progress and address any blockers. Here, the Sprint Backlog plays a crucial role by tracking each story's status and helping the Team stay focused on the Sprint Goal.
During the Daily Scrum, each Team member shares what they completed the previous day, their plans for the current day, and any obstacles they are facing. This quick exchange keeps everyone informed, fosters accountability and allows the Scrum Master to identify and remove blockers. The Product Owner may observe these meetings to stay updated, while the Scrum Master ensures they remain efficient and focused.
Sprint Review
The Sprint Review takes place at the end of each Sprint, providing an opportunity for the Team to demonstrate the Increment - the sum of all completed and potentially shippable features. This artifact represents tangible progress, delivering value as a working piece of the product.
During the Sprint Review, the Team showcases completed stories to the Product Owner, stakeholders, and users, gathering feedback that may influence future iterations. The Product Owner updates the Product Backlog based on this feedback, adding new user stories or adjusting existing ones to ensure continuous alignment with user needs. This event reinforces the Scrum principles of transparency and inspection by involving stakeholders in real-time project progress and demonstrating incremental value.
While not defined as a regular Scrum event, Backlog refinement is a crucial part of the Scrum process. It is typically carried out after Sprint review to ensure the Backlog is well-defined, prioritized, and estimated, ultimately supporting effective Sprint Planning.
Retrospective
The Retrospective is a final event in each Sprint, dedicated to evaluating the Team’s performance and identifying areas for improvement. Unlike the Sprint Review, which focuses on product output, the Retrospective centers on the process. Here, the Team reflects on the Sprint’s successes, challenges, and potential changes for the next iteration.
During this meeting, the Scrum Master guides the Team in pinpointing what went well and what could improve and how. This feedback loop encourages open communication and supports the Scrum value of continuous improvement. While no specific artifact is directly associated with the Retrospective, its outcomes often lead to changes in how the Product Backlog is managed or how the Team approaches Sprint Planning and execution.
Each Scrum event is strategically designed to guide the Team through planning, progress tracking, feedback, and continuous improvement. The Product Backlog, Sprint Backlog, and Increment play pivotal roles across these events, ensuring that all activities are aligned with delivering maximum value and meeting the Sprint Goal. These events and artifacts create a dynamic and adaptive cycle, allowing the Team to respond to new information and evolving requirements while maintaining a focus on delivering value with every Sprint.
Resources
Sound interesting?
Contact our expert Vesa or fill in the form below and let us contact you.
