Sizing Product Backlog Items
As Developers are the ones who need to do the work, they are the people who are responsible for the sizing of the work. There are various techniques teams may use to size their Product Backlog items such as:
- Absolute - often time-based; for example, “This PBI will take 9 hours of work”
- Relative - uses a scale that lets developers estimate the size of the PBIs relative to each other; for example, story points or t-shirt sizing
- Right sizing - identifies items that are small enough to be completed within one single Sprint; for example, Developers discuss if they can complete a PBI according to their Definition of Done comfortably within one Sprint, if not they should break down the PBI
The Developers should choose whichever sizing method makes most sense for them as a team.
What did you think about this content?
Included In
Learning Series
Product Backlog Management is the act of adjusting and ordering items on the Product Backlog so that the Scrum Team can deliver the most valuable product possible. This learning series explores Product Backlog Management.