This article is terse because it presents estimating in Scrum as quickly as possible. I assume that the reader has a basic understanding of Scrum. If you’re new to Scrum, this video by Lyssa Adkins explains Scrum in ten minutes.
Reader Interactions
Comments
Trackbacks
-
[…] PBI contains a description, order and estimate. It may optionally contain a group descriptor, if more than one Scrum Team is using the Product […]
-
[…] Ensuring the Development Team understands items in the Product Backlog to the level needed. […]
-
[…] a Description of what was wanted, an Order relative to the other items, a business Value and an Estimate. There are different techniques for doing all of these and I’ll cover that in a separate […]
-
[…] you use relative size estimating for your product backlog items, your estimating won’t need to change. The reason is that your […]
-
[…] the easiest way to estimate a new story is to compare it against the other stories that you already have in your Product […]
Hi Derek,
I completely agree that the key outcome is to get some relative sizing of the backlog.
I would suggest that one of the most crucial things in the estimation is the discussion – so that the Dev Team and the Product Owner both gain a deeper understanding of what is being requested.
As the understanding of the business value is increased, they may break the story down further, add more detailed acceptance criteria, and enrich the PBI with more information.
Regards
Simon