Scrum Methodology
Learn Scrum
The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.
5th
SEP
The Scrum Backlog
Posted by admin under Scrum Basics
Scrum has two types of backlogs, the Product Backlog, and the Sprint Backlog.
The Product Backlog is a prioritized list of customer-centric features. It breaks the big-picture vision down into manageable increments of work called Product Backlog Items (PBIs). These are typically expressed in user story form. Product Backlog Items are not tasks, they represent the what rather than the how. If Product Backlog Items are estimated, they’re estimated in relative units such as story points. Items toward the top of the Product Backlog should be small enough that a team could accomplish several of them (including proper testing, integration, etc.) in one two-week Sprint.
The Product Owner and Team collaborate to refine the Product Backlog continuously (e.g. about an hour per week) in the Backlog Refinement Meeting.
In Large Scale Scrum, multiple teams pull their work from a single Product Backlog. Multiple teams collaborate with the Product Owner to refine the single Product Backlog.
The Sprint Backlog is created during the Sprint Planning Meeting. The team pulls the amount of work they want to do from the Product Backlog into the Sprint Backlog, and further decomposes the PBIs into Sprint Tasks. The team decides the how, and expresses this in the tasks. The best way to represent the Sprint Backlog is a physical taskboard, using PostIt Notes or index cards. During the Sprint, typically at the Daily Scrum Meeting, team members move the tasks around to reflect how they’re doing on them. One purpose of the Sprint Backlog is to limit work in progress (WIP). Humans become ineffective when they worry about too many things at the same time.
Tags: backlog items, scrum backlog, scrum backlog items, Scrum Methodology, scrum PBIsScrum Training Series
Recent Posts
- Scrum based funding model – 20 percent May 9, 2013
- The Next Big Idea March 5, 2013
- On Being Available February 17, 2013
- Should Scrum Always Require the Product Owner to Attend the Sprint Retrospective Meeting? February 5, 2013
- Happiness Metrics January 23, 2013
Archives
- May 2013 (1)
- March 2013 (1)
- February 2013 (2)
- January 2013 (2)
- December 2012 (3)
- November 2012 (1)
- January 2012 (1)
- December 2011 (2)
- November 2011 (3)
- October 2011 (2)
- November 2010 (1)
- September 2010 (1)
- June 2010 (1)
- April 2010 (1)
- March 2010 (1)
- February 2010 (1)
- December 2009 (3)
- November 2009 (2)
- October 2009 (4)
- September 2009 (4)
- August 2009 (2)
- July 2009 (2)
- June 2009 (2)
- May 2009 (2)
- April 2009 (2)
- March 2009 (5)
- February 2009 (2)
- January 2009 (2)
- December 2008 (4)
- November 2008 (3)
- October 2008 (4)
- September 2008 (4)
- August 2008 (1)
Categories
- Agile and Scrum (32)
- Agile Assessment (2)
- Agile Manifesto (6)
- Agile Principles (10)
- Scrum Basics (45)
- Scrum Discussion (28)
- Scrum Transitions (19)
- transformation (5)
- Uncategorized (10)