Posted in Scrum Artifacts

Product Backlog


“It is the single source of requirements for any changes to be made to the product.” (1)


Overview

Definition: The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for the product (2, pg 46)

Owner: Product Owner is responsible

Product Backlog Characteristics

  • Exists as long as the Product exists
  • One single list for everything
  • One Product = One Product Backlog = One Product Owner (2, pg 46)
  • Grows as marketplace feedback is received, product gains value, technology changes etc

Product Backlog Contents

  • Product Backlog Items of all changes to be made to the Product including
    • Features
    • Functions
    • Requirements
    • Enhancements
    • Fixes

Product Backlog Items

  • Description, Order, Estimate, and Value
  • Product Backlog items often include test descriptions that will prove its completeness when “Done”

Product Backlog Refinement

Definition: Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog.

Length: “Refinement usually consumes no more than 10% of the capacity of the Development Team” (1)

People: Product Owner, Development Team

Outcome: Product Backlog items become more transparent through refinement and the top items are deemed ‘Ready’ for a Sprint (i.e. can be ‘Done’ by the team within one Sprint)

Product Backlog Details

  • Greater clarity and detail on the items higher up the order

Product Backlog Estimates

  • ‘More precise’ estimates (1) are made with greater clarity (i.e. higher up the backlog order)
  • Development Team is responsible for all estimates
    • Product Owner may support in collaboration

Product Backlog Order

  • Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones

Monitoring Progress Toward Goals

  • Product Owner is responsible for monitoring progress and making this transparent to Stakeholders
  • Remaining total work to reach a goal can be summed at any point
  • The Product Owner tracks work remaining at least every Sprint Review and compares to previous Sprint Reviews to assess progress toward completing work by the desired time for the goal. 

Monitoring Practices

NOTE: No practice replaces the importance of empiricism. In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision-making.

  • burn-downs
  • burn-ups
  • cumulative flows

Extra: Product Journey

  1. What is the business direction?
  2. Focus on who your target customer is (my notes coming soon)
  3. Focus on what the problem is
  4. Prioritise which problem to fix
  5. Form a hypothesis
  6. Test your hypothesis
  7. Communicate your Product Vision
  8. Create the Product Backlog
  9. Prioritising the Product Backlog
  10. Build your MVP
  11. Monitoring progress towards a goal through roadmaps
  12. Refine the Product Backlog

References

  1. The Scrum Guide
  2. Scrum Insights for Practitioners by Hiren Doshi

Explore Other Scrum Artifacts

Sprint BacklogIncrement
Posted in Scrum Artifacts

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 realising the Sprint Goal.”(1)


Overview

Definition: The Sprint Backlog is the set of PBIs selected for the Sprint, plus a plan, often a list of tasks, for delivering the Product Increment and realising the Sprint Goal.

Owner: The Development Team

Sprint Backlog Contents

  • Product Backlog Items + Plan = Sprint Backlog
  • at least one high priority process improvement from the previous Retrospective

Emergence

  • The Sprint Backlog emerges during the Sprint as the Development team learns more about what is needed to achieve the Sprint Goal
  • If new work is required it is added by the Development Team
  • As work is completed the estimated remaining work is updated by the Development Team
  • If work is no longer necessary it is removed by the Development Team

Monitoring Sprint Progress

  • Total work remaining in the Sprint Backlog can be summed at any time in the Sprint
  • Progress is monitored at least every Daily Scrum and aids the conversations regarding the likelihood of achieving the Sprint Goal
  • The Development Team monitors its own progress

References

  1. The Scrum Guide
  2. Mastering Professional Scrum by Stephanie Ockerman and Simon Reindl

 


Explore Other Scrum Artifacts

Product Backlog Increment

 

Posted in Scrum Artifacts

Increment


“The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.” (1)


Overview

Definition: The increment is the cumulative sum of all the PBIs completed during the Sprint and the value of the increments of all the previous Sprints (pg 49, Scrum Insights for Practitioners)

  • An Increment must be “Done” at the end of a Sprint
  • An Increment is a step towards the product vision
  • An Increment must be usable
  • An Increment is released if decided by the Product Owner

Releasing

Release Size (3, pg 113)

The smallest release you should consider is a new or improved outcome for a single persona. Any smaller the effort to release is not worth it for your customers.


References

  1. The Scrum Guide
  2. Scrum Insights for Practitioners by Hiren Doshi
  3. Mastering Professional Scrum by Stephanie Ockerman and Simon Reindl

Explore Other Scrum Artifacts

Product Backlog Sprint Backlog