the final words about software estimation
DESCRIPTION
Slides of my Pecha Kucha short talk at #ALE14 in Krakow. There's too much noise around software estimation, and one of the problem is that we try to use the same approach, when we're in practice estimating totally different things.TRANSCRIPT
The final words about software estimationEven broken models can teach us something
@ziobrando
They may be right, sometimes
11 x 2 = …
“It’s only a couple of mines somewhere…”
Software development is a learning process
Working code is a side effect
Learning is crucial for our job, and yet we don’t
know much about it
Look inside!
Learning is non linear
(doesn’t fit into spreadsheets, burndown and Gantt charts)
Learn!
Can you estimate learning?
Value Stream Mapping
http://agile.dzone.com/books/continuous-delivery-free
Coding 20cl, learning 20cl, deciding 20cl, waiting...
Can you estimate waiting?
Deciding?
We suck at it
Should I marry her?
Yes No
Deadline!
...but can we stop afterthoughts?
SummaryRepeatable (boring) —> Pseudo-linear
Legacy —> Too guilty to accept the real numbers
Learning —> Non Linear
Deciding —> Deadlines & acceptable results
Waiting —> Remove coupling