Timeline for In scrum should incomplete stories be re-estimated or does the original estimate get burned down when it's finally completed?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2015 at 17:06 | comment | added | WBW | Story points and velocity will not tell you how much value is added over time. The product owner's estimation of story priority or rank is a closer proxy to customer value. A team with increasing velocity or a team with a higher velocity than a different team does not indicate that the team is delivering more value. Scrum teams commit to delivering stories and indirectly commit to delivering value. It's more the customer or PO that is responsible for ensuring the commitment contains the right stories that optimize value delivery. | |
| Aug 6, 2015 at 8:42 | comment | added | Willl | It's a good point about 'credit' for work done. That's a big change for lots of people (extra context: the team in this case is offshore, which complicates things a little in this regard). I don't agree that the planning element of estimation should be considered an afterthought though. Yes, owning and understanding commitment is crucial but the purpose of that commitment is partly to know how much value is added over time and the reason you need to know that is so you can plan around it as a business. | |
| Aug 5, 2015 at 23:38 | history | answered | WBW | CC BY-SA 3.0 |