Transcript
Page 1: The final words about software estimation

The final words about software estimationEven broken models can teach us something

@ziobrando

Page 2: The final words about software estimation

They may be right, sometimes

Page 3: The final words about software estimation

11 x 2 = …

Page 4: The final words about software estimation
Page 5: The final words about software estimation
Page 6: The final words about software estimation

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

Page 7: The final words about software estimation

Software development is a learning process

Working code is a side effect

Page 8: The final words about software estimation

Learning is crucial for our job, and yet we don’t

know much about it

Look inside!

Page 9: The final words about software estimation

Learning is non linear

(doesn’t fit into spreadsheets, burndown and Gantt charts)

Page 10: The final words about software estimation

Learn!

Page 11: The final words about software estimation

Can you estimate learning?

Page 12: The final words about software estimation

Value Stream Mapping

http://agile.dzone.com/books/continuous-delivery-free

Page 13: The final words about software estimation

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

Page 14: The final words about software estimation

Can you estimate waiting?

Page 15: The final words about software estimation

Deciding?

Page 16: The final words about software estimation

We suck at it

Page 17: The final words about software estimation

Should I marry her?

Yes No

Page 18: The final words about software estimation

Deadline!

Page 19: The final words about software estimation

...but can we stop afterthoughts?

Page 20: The final words about software estimation

SummaryRepeatable (boring) —> Pseudo-linear

Legacy —> Too guilty to accept the real numbers

Learning —> Non Linear

Deciding —> Deadlines & acceptable results

Waiting —> Remove coupling