The document discusses the complexities of software estimation, emphasizing that even flawed models can provide insights. It highlights that learning in software development is non-linear and cannot be easily quantified or scheduled like traditional project management tools. The author suggests reevaluating our approaches to estimating learning, decision-making, and waiting within the development process.

1. The final words about
software estimation
Even broken models can teach us something
@ziobrando

2. They may be right, sometimes

3. 11 x 2 = …

6. “It’s only a couple of
mines somewhere…”

7. Software
development is a
learning process
Working code is a
side effect

8. Learning is crucial for
our job, and yet we don’t
know much about it
Look inside!

9. Learning is non
linear
(doesn’t fit into spreadsheets, burndown and Gantt charts)

10. Learn!

11. Can you estimate
learning?

12. Value Stream Mapping
http://agile.dzone.com/books/continuous-delivery-free

13. Coding 20cl, learning 20cl,
deciding 20cl, waiting...

14. Can you estimate
waiting?

15. Deciding?

16. We suck at it

17. Should I marry her?
Yes
No

18. Deadline!

19. ...but can we stop
afterthoughts?

20. Summary
Repeatable (boring) —> Pseudo-linear
Legacy —> Too guilty to accept the real
numbers
Learning —> Non Linear
Deciding —> Deadlines & acceptable
results
Waiting —> Remove coupling