2.2 Scrum artifacts (Product Backlog, Sprint Backlog, Increment)
4 min read•august 13, 2024
Scrum artifacts are key tools that provide transparency and opportunities for inspection and adaptation. The , , and work together to ensure the team delivers value in each Sprint.
These artifacts help the Scrum Team stay focused on their goals and track progress. By managing and refining these artifacts, teams can improve their ability to deliver high-quality products that meet customer needs.
Scrum Artifacts
Product Backlog Purpose and Structure
Top images from around the web for Product Backlog Purpose and Structure
Projecte Gestor de projectes SCRUM - Wiket View original
Is this image relevant?
Scrum (software development) - Wikipedia View original
Is this image relevant?
Free Scrum Task Board PowerPoint Template - Free PowerPoint Templates - SlideHunter.com View original
Is this image relevant?
Projecte Gestor de projectes SCRUM - Wiket View original
Is this image relevant?
Scrum (software development) - Wikipedia View original
Is this image relevant?
1 of 3
Top images from around the web for Product Backlog Purpose and Structure
Projecte Gestor de projectes SCRUM - Wiket View original
Is this image relevant?
Scrum (software development) - Wikipedia View original
Is this image relevant?
Free Scrum Task Board PowerPoint Template - Free PowerPoint Templates - SlideHunter.com View original
Is this image relevant?
Projecte Gestor de projectes SCRUM - Wiket View original
Is this image relevant?
Scrum (software development) - Wikipedia View original
Is this image relevant?
1 of 3
- The Product Backlog is an ordered list of everything needed in the product
- Serves as the single source of requirements for any product changes
- The Product Backlog is dynamic and constantly evolving
- Identifies what the product needs to be appropriate, competitive, and useful
- The Sprint Backlog is a set of Product Backlog items selected for the Sprint
- Includes a plan for delivering the product Increment and realizing the Sprint Goal
- The Increment is the sum of all completed Product Backlog items during a Sprint
- Includes the value of increments from all previous Sprints (cumulative)
- Each Increment is additive and thoroughly verified to ensure they work together (integration)
Sprint Backlog and Increment Characteristics
- The Sprint Backlog is a forecast by the Development Team
- Defines what functionality will be in the next Increment
- Outlines the work needed to deliver that functionality into a "Done" Increment
- The Sprint Backlog makes visible all work the Development Team deems necessary to meet the Sprint Goal
- Provides enough detail that progress changes can be understood in the Daily Scrum (transparency)
- The Increment must be in useable condition regardless of whether the decides to it
- Multiple Increments may be created within a Sprint ()
- The sum of the Increments is presented at the Sprint Review to support empiricism (inspect and adapt)
Product Backlog Management
Product Owner Responsibilities
- The Product Owner is responsible for the Product Backlog content, availability, and ordering
- Ensures the Product Backlog is visible, transparent, and clear to all (accessibility)
- Product is an ongoing process
- The Product Owner and Development Team collaborate on Product Backlog item details
- Items are reviewed and revised during refinement (continuous improvement)
- The Scrum Team decides how and when refinement is done (self-management)
Product Backlog Refinement Practices
- Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones
- More precise estimates are assigned based on greater clarity and increased detail (estimation accuracy)
- Product Backlog items for the upcoming Sprint are refined
- Refined in enough detail so any one item can reasonably be "Done" within the Sprint time-box (Sprint Planning)
- Examples of Product Backlog items: user stories, use cases, requirements, specifications
- Techniques for refinement: story mapping, user story workshops, backlog grooming sessions
Sprint Backlog Derivation
Creating the Sprint Backlog
- The Sprint Backlog is derived from the Product Backlog
- Product Backlog items are selected for the Sprint based on priority and team capacity
- The Development Team forecasts what functionality will be developed during the Sprint
- Functionality is based on the selected Product Backlog items and the Sprint Goal
- The Development Team determines the work needed to deliver the forecasted functionality into a "Done" Increment
- The work is added to the Sprint Backlog as a plan for the Sprint
Modifying the Sprint Backlog
- The Development Team modifies the Sprint Backlog throughout the Sprint as more is learned
- The Sprint Backlog emerges during the Sprint based on Development Team discoveries (empiricism)
- As new work is required, the Development Team adds it to the Sprint Backlog
- As work is performed or completed, the estimated remaining work is updated (burndown)
- The Sprint Backlog is a highly visible, real-time picture of the Sprint work
- Shows the work the Development Team plans to accomplish (commitment)
- Ensures transparency of the Development Team's progress towards the Sprint Goal
Increment Deliverables
Potentially Releasable Increments
- A potentially releasable Increment is delivered at the end of each Sprint
- The Increment is in useable condition regardless of whether the Product Owner decides to release it
- Delivering a releasable Increment each Sprint ensures the team is working on the most valuable features
- Allows the team to pivot if needed based on feedback (agility)
- Enables faster time to market and quicker return on investment (business value)
- Examples of Increments: working software, integrated hardware components, tested product enhancements
Benefits of Regular Increments
- Having a usable Increment each Sprint provides the option to release to customers anytime
- The Product Owner can choose to release the product when it makes sense for the business
- Consistently delivering a releasable Increment builds trust with stakeholders
- Demonstrates the Scrum Team's ability to regularly produce working, high-quality product functionality
- Delivering Increments supports empiricism and Scrum values
- Shows evidence of the Scrum Team's progress (transparency)
- Allows the Scrum Team to inspect results and adapt as needed (inspection and adaptation)
- Requires focus, openness, respect, courage and commitment to deliver value each Sprint
Key Terms to Review (17)
Backlog refinement: Backlog refinement is the ongoing process of reviewing and updating the product backlog to ensure that it remains relevant, prioritized, and ready for future sprints. This practice involves adding new items, clarifying existing ones, estimating effort, and ensuring that the backlog items align with the project's goals. Effective backlog refinement not only keeps the development team focused on the most important tasks but also enhances collaboration with stakeholders, ensuring that everyone has a clear understanding of priorities and requirements.
Burn-down chart: A burn-down chart is a visual tool used in Agile project management to track the amount of work remaining in a project over time, typically displayed in a graph format. It helps teams monitor their progress toward completing work within a sprint or project and provides insights into whether they are on track to meet deadlines.
Creation: In the context of project management, creation refers to the process of developing and establishing foundational elements that will guide the team's work. This encompasses the formulation of various artifacts that represent requirements, plans, and deliverables. By effectively creating these artifacts, teams can align their vision and objectives, ensuring that everyone is on the same page and fostering collaboration throughout the project lifecycle.
Definition of Done: The Definition of Done is a clear and concise checklist that outlines the criteria that must be met for a product increment to be considered complete. This helps ensure that everyone on the team has a shared understanding of what it means for work to be finished and contributes to maintaining high quality in deliverables. It plays a crucial role in aligning the team’s expectations, guiding work during development, and providing clarity for the acceptance of completed items.
Estimation Techniques: Estimation techniques are methods used to assess the effort, time, and resources needed to complete a project or task in Agile project management. These techniques help teams make informed decisions about prioritization and planning by providing a clearer understanding of the workload involved. They are essential for creating and managing key components like the Product Backlog and Sprint Backlog, ensuring that teams can effectively allocate their capacity and meet delivery goals during various Scrum events.
Increment: An increment is a tangible, usable piece of software that is delivered at the end of each iteration, known as a sprint, in Agile methodologies like Scrum. Each increment builds on the previous increments, adding new features or improving existing ones, which enables the team to gradually refine and expand the product while ensuring that each version is potentially shippable.
Iterative Development: Iterative development is a software development process that builds and improves products through repeated cycles, or iterations. Each iteration typically involves a portion of the overall project that is developed, tested, and evaluated before moving on to the next segment, allowing teams to refine their work based on feedback and changing requirements.
Kanban Board: A Kanban board is a visual tool used in project management to display work items and their progress through various stages of a workflow. It helps teams track tasks, improve efficiency, and manage workflow by providing a clear overview of what needs to be done, what is currently in progress, and what has been completed. This board plays a significant role in promoting collaboration, identifying bottlenecks, and facilitating effective communication within teams.
Maintenance: Maintenance refers to the ongoing process of managing, updating, and refining a product or project after its initial delivery. It involves ensuring that the product continues to meet user needs and expectations through enhancements, bug fixes, and performance improvements. This process is crucial for the longevity and effectiveness of the product as it adapts to changes in user requirements or market conditions.
Prioritization: Prioritization is the process of determining the order of importance for tasks or features, guiding teams on what to focus on first to maximize value and efficiency. It plays a critical role in managing limited resources and ensuring that the most valuable work is completed promptly. This concept is essential in Agile methodologies, influencing how teams handle backlogs and plan transformations.
Product Backlog: The product backlog is a prioritized list of features, enhancements, bug fixes, and technical work that needs to be completed for a product. It serves as a dynamic roadmap that guides the development team and stakeholders in delivering value, aligning closely with the principles of collaboration and customer satisfaction.
Product Owner: The Product Owner is a key role in Agile project management, specifically within the Scrum framework, responsible for maximizing the value of the product resulting from the work of the development team. This role acts as a bridge between stakeholders and the development team, ensuring that the product backlog is prioritized and that user stories reflect the needs and expectations of users and stakeholders.
Release: In Agile Project Management, a release refers to a version of a product that is made available to users after a series of iterations or sprints. This term is crucial because it connects the development process to user feedback and market needs, ensuring that the product evolves based on real-world use. A release typically contains features that have been completed and tested, offering tangible value to customers while allowing teams to prioritize work through artifacts like the Product Backlog and Sprint Backlog.
Scrum Master: A Scrum Master is a facilitator and servant leader for a Scrum team, responsible for ensuring that the team adheres to Agile practices and principles while helping to remove any obstacles that may impede progress. This role is crucial in fostering an environment of collaboration, accountability, and continuous improvement within the team.
Sprint Backlog: The sprint backlog is a prioritized list of tasks and items that a Scrum team commits to completing during a specific sprint. It is derived from the product backlog and serves as a clear plan for the development team, helping them focus on delivering specific functionalities and improvements within the sprint timeframe.
Value Delivery: Value delivery refers to the process of providing beneficial outcomes to stakeholders through the completion of work in a timely and efficient manner. It emphasizes maximizing the benefits of a project by aligning its objectives with customer needs and ensuring that the delivered products or services meet quality standards. This concept is central to methodologies that focus on continuous improvement and customer satisfaction, which are key in managing projects effectively.
Velocity: Velocity is a key metric in Agile project management that measures the amount of work a team completes in a given iteration, typically expressed in story points. This measurement allows teams to gauge their productivity and predict future performance, making it an essential tool for planning and improving efficiency in Agile practices.