5. In 1986, Profs. S.D. Conte, H.E. Dunsmoir, and V.Y.
Shen proposed that a good estimation approach
should provide estimates that are within 25% of
the actual results 75% of the time
--Steve McConnel, Software Estimation: Demystifying the Black Art
5
6. Who has delivered a project ?
- on time
- within budget
- what was requested
within 25%
6
7. Who has delivered 7,5 out of 10 projects?
- on time
- within budget
- what was requested
within 25%
7
56. Estimates assume we are in an Ordered Domain, where
reductionism works. Software however is in the Complex
and Complicated domain where reductionism does not
work. #NoEstimates
57. rules of #NoEstimates
1. Select the most important piece of work you need to do
2. Break that work down into risk neutral pieces of work
3. Develop each piece of work
4. Iterate and refactor
5. ( Count for predictability )
60. imaging 17 September 2016
you have been doing #NoEstimates for a while.
What have you learned?
workshop
61. 61
workshop
What did not work?
What were the challenges?
What worked?
What were the advantages?
imaging 17 September 2016
you have been doing #NoEstimates for a while.
What have you learned?
62. 62
workshopimaging 17 September 2016
you have been doing #NoEstimates for a while.
What have you learned?
What did not work?
What were the challenges?
What worked?
What were the advantages?
63. 63
workshoppick a side
- what you prefer
- what you disagree with
- to make it even..
What did not work?
What were the challenges?
What worked?
What were the advantages?