How to explain why Story Points are better for estimation using a little story: My Ideal Days Are Not Your Ideal Days Suppose two runners, one fast and one slow, are standing at the start of a trail. Each can see the whole course of the trail and they can agree that it is 1… Read Article →
Posts Tagged: Estimation
The Right Amount of Discussion Some amount of preliminary design discussion is necessary and appropriate when estimating. However, spending too much time on design discussions sends a team too far up the accuracy/effort curve of Figure 6.1. Here’s an effective way to encourage some amount of discussion but make sure that it doesn’t go on… Read Article →
I found a super nice story to illustrate this: How many Elephant Points are there in the veldt? Let’s conduct a poll of the herds. Herd A reports 50,000 kg. Herd B report 84 legs. Herd C reports 92,000 lb. Herd D reports 24 head. Herd E reports 546 elephant sounds per day. Herd F… Read Article →
When should we use which method? Here´s my approach 🙂 Magic Estimation vs. Planning Poker When it comes to estimation it does make a difference which method we use. Magic Estimation very good for high level estimation of a whole backlog for example at the start of project estimating more than ca. 15 user stories it… Read Article →
Auch ein netter Beitrag zu Estimation: “Dynamic Magic Estimation – Funktionalität schätzen 3.0”
Need a set of planning poker cards? Here´s a fun one you can print: https://rthewitt.com/2017/02/01/emojination-cards/
Here´s a list of mechanisms causing estimation errors – Watch out for them when your team estimates user stories: As a scrum master you could introduce one of these biases is every retrospective and ask the team to find strategies to avoid them. Causes for estimation error Mechanisms Cone of uncertainty Requirements creep Garbage in… Read Article →
Some more biases you can discus with your team in a retrospective: bandwagoneffect expectancy bias emerging preferences response bias priming effect halo effect anchoring effect