| Context | Product Backlog Items need to be estimated realistically. |
| Problem | How do I get reliable estimates? Often, estimates are produced by people, who do not know the work to be done in depth or forget important aspects like testing. |
| Forces | too little/too much overhead too little/too much detail planning |
| Solution | Let the people estimate who do the actual work. The people, who do the work usually know best, how much effort it requires. However, the same people usually calculate a buffer, sometimes even without knowing it. So, estimates need to be challenged. This should be done by asking for a team estimate, e.g. in a Product Backlog Grooming Meeting or in a Sprint Planning Meeting. In Scrum, the estimate is done by Pigs, not by Chickens. |
| Resulting Context | The Product Backlog Items are estimated. |
Dieser Artikel wurde von Andreas Heilwagen am 23.05.2011 um 17:15 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
Product Backlog Items are estimated and Sprint Backlog Tasks are also estimated. These two estimates despite some similarities are used for very different purposes….Scrum advocates estimating the Product Backlog Items Work Queue using relative points. All other items are estimated relative to this item…For the Sprint Backlog Tasks the estimation is usually done in ideal hours .