Clients need to know how much a project will cost. Waterfall development is always late and over-budget. Agile development is done when it's done. You're left with estimates that you know are too low and then you squeeze them anyway. It shouldn't be this way. We'll look at how this happens, early warning signs, ways out and ways of avoiding it in the first place.
25. Estimate a day as 8 hours
●
16 hr. task == 2 days
(ha ha – you're cute)
26. Estimate a day as 8 hours
●
16 hr. task == 2 days
(ha ha – you're cute)
●
You are not a code
machine
27. Estimate a day as 8 hours
●
16 hr. task == 2 days
(ha ha – you're cute)
●
You are not a code
machine
●
Even if you are,
your team is not
28. Estimate a day as 8 hours
●
16 hr. task == 2 days
(ha ha – you're cute)
●
You are not a code
machine
●
Even if you are,
your team is not
●
Dev: 6 hr. Lead: 4 hr.
48. Agile means we can't estimate
“Yeah, well, you know, that's just like, your opinion, man.”
49. Agile means we can't estimate
●
Over-reaction to
Waterfall
“Yeah, well, you know, that's just like, your opinion, man.”
50. Agile means we can't estimate
●
Over-reaction to
Waterfall
●
Excuse to drop
software engineering
and just hack it
“Yeah, well, you know, that's just like, your opinion, man.”
79. Estimate bugs
●
“Nein, nein, nein! Das
ist verboten!”
-- @dzuelke
80. Estimate bugs
●
“Nein, nein, nein! Das
ist verboten!”
-- @dzuelke
●
You do not know the
size of the problem
81. Estimate bugs
●
“Nein, nein, nein! Das
ist verboten!”
-- @dzuelke
●
You do not know the
size of the problem
●
Spend 3 days
investigating –
change 1 line of code