Difference between revisions of "Estimate"

From Pearl Language
Jump to navigation Jump to search
(Use {{p|yesterday’s weather}})
m (David J. Anderson)
 
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{quote|When we praise and glorify the team working late to meet speculative estimates, we destroy life and corrupt the culture of the company.|@zenagilist}}
{{quote|Just start referring to “estimates” as lies. “How long will that take?” “Well, if I had to lie, a week?”|@trek}}
{{quote|Alternative to estimates: do the most important thing until either it ships or it is no longer the most important thing.|Kent Beck}}
{{quote|In preparing for [projects] I have always found that [estimates] are useless, but [estimating] is indispensable.|General Dwight D. Eisenhower}}
{{quote|In preparing for [projects] I have always found that [estimates] are useless, but [estimating] is indispensable.|General Dwight D. Eisenhower}}
{{quote|It’s better to be roughly right than precisely wrong|Maynard Keynes}}
{{quote|It’s better to be roughly right than precisely wrong|Maynard Keynes}}
Line 5: Line 11:


{{quote|Insanity: Doing the same thing over and over and expecting different results.|Albert Einstein}}
{{quote|Insanity: Doing the same thing over and over and expecting different results.|Albert Einstein}}
{{quote|Ask, “Is the estimate useful?” rather than “Is the estimate right or wrong?”|Chris Matts}}


Watch out for:
Watch out for:
Line 13: Line 21:
Collect metrics about the real system, like {{p|average lead time distribution}}, {{p|cumulative flow diagram}}, {{p|average throughput}}, and {{p|predictability}}.
Collect metrics about the real system, like {{p|average lead time distribution}}, {{p|cumulative flow diagram}}, {{p|average throughput}}, and {{p|predictability}}.


*→ {{p|metrics drive behavior}}
Thou shalt not treat estimates as commitments.
*→ {{p|relative estimation}}
 
*http://www.djaa.com/noestimates-beef-and-agiles-trojan-horse
Setting deadlines and promises based on estimates is dysfunctional.
*[https://twitter.com/noestimates #noestimates]
 
*http://en.wikipedia.org/wiki/Probabilistic_method
The problem with estimates isn’t so much the concept of estimates themselves—because they are fine if we know that they are estimates—but that the way we treat them in software is not like an estimate. They drive deadlines and they drive promises and because of this, we get all kinds of problems.
*http://www.infoq.com/articles/software-development-effort-estimation
*http://softwaredevelopmenttoday.blogspot.co.nz/2012/01/story-points-considered-harmful-or-why.html
*http://www.infoq.com/resource/minibooks/emag-agile-estimation/en/pdf/Agile-Project-Estimation-and-Planning-eMag.pdf


See {{p|plastic plan}}.
==Sources==
*{{see|{{verb|budget}}}}
*{{see|{{p|metrics drive behavior}}}}
*{{see|{{p|relative estimation}}}}
*{{see|{{p|plastic plan}}}}
{{WebSourceListItem
|url=http://toddlittleweb.com/wordpress/2016/03/14/to-estimate-or-noestimates-that-is-the-question-2/
|site=Todd’s blog
|person=Todd Little
|title=To Estimate or #NoEstimates, that is the Question
}}
{{WebSourceListItem
|url=http://noestimatesbook.com/wp-content/uploads/2014/11/NoEstimates-book-Chapter-1-We-suck-at-estimation.pdf
|site=The IT Risk Manager
|person=Vasco Duarte
|title=No Estimates—How To Measure Project Progress Without Estimating
}}
{{WebSourceListItem
|url=http://theitriskmanager.wordpress.com/2014/12/07/cynefin-and-estimates/
|site=The IT Risk Manager
|person=Chris Matts
|title=Cynefin and Estimates
}}
{{WebSourceListItem
|url=http://www.djaa.com/noestimates-beef-and-agiles-trojan-horse
|site=David J. Anderson & Associates
|person=David J. Anderson
|title=The #NoEstimates Beef! And Agile's Trojan Horse
}}
{{WebSourceListItem
|url=https://twitter.com/noestimates #noestimates
|site=Twitter
|title=Twitter/#noestimates
}}
{{WebSourceListItem
|url=http://en.wikipedia.org/wiki/Probabilistic_method
|site=Wikipedia
|title=Probabilistic method
}}
{{WebSourceListItem
|url=http://www.infoq.com/articles/software-development-effort-estimation
|site=InfoQ
|person=Magne Jorgensen
|title=What We Do and Don't Know about Software Development Effort Estimation
}}
{{WebSourceListItem
|url=http://softwaredevelopmenttoday.blogspot.co.nz/2012/01/story-points-considered-harmful-or-why.html
|site=Software Development Today
|person=Vasco Duarte,Joseph Perline
|title=Story Points Considered Harmful—Or why the future of estimation is really in our past…
}}
{{WebSourceListItem
|url=http://www.infoq.com/resource/minibooks/emag-agile-estimation/en/pdf/Agile-Project-Estimation-and-Planning-eMag.pdf
|site=InfoQ
|title=Agile Project Estimation and Planning
|kind=pdf
}}
{{WebSourceListItem
|url=http://focusedobjective.com/forecasting-error-accounting-scope-increase/
|site=Focused Objective
|person=Troy Magennis
|title=Forecasting Error: Not Accounting For Scope Increase
}}
{{WebSourceListItem
|url=http://lizkeogh.com/2013/07/21/estimating-complexity/
|site=Liz Keogh
|title=Estimating Complexity
}} see also {{p|cynefin}}
{{WebSourceListItem
|url=http://www.infoq.com/articles/noestimates-monte-carlo
|site=InfoQ
|person=Dimitar Bakardzhiev
|title=#NoEstimates Project Planning Using Monte Carlo Simulation
}}
{{WebSourceListItem
|url=http://www.infoq.com/presentations/monte-carlo-simulation
|site=InfoQ
|person=Dimitar Bakardzhiev
|title=#noestimates Project Planning Using Monte Carlo Simulation
}}
{{WebSourceListItem
|url=http://codemanship.co.uk/parlezuml/blog/?postid=1316
|site=Codemanship
|person=Jason Gorman
|title=My First, Last & Only Blog Post About #NoEstimates
}}
{{WebSourceListItem
|url=http://ronjeffries.com/articles/015-jul/mcconnell/
|site=Ron Jeffries
|title=Steve McConnell on #NoEstimates
}}
{{WebSourceListItem
|url=http://www.construx.com/10x_Software_Development/_NoEstimates_-_Response_to_Ron_Jeffries/
|site=Construx
|person=Steve McConnell
|title=#NoEstimates - Response to Ron Jeffries
}}
{{WebSourceListItem
|url=http://ronjeffries.com/articles/015-jul/mcconnell-2b/
|site=Ron Jeffries
|title=Continued Discussion with Steve McConnell
}}
{{WebSourceListItem
|url=http://www.mountaingoatsoftware.com/blog/budget-when-you-cant-estimate
|site=Mike Cohn
|title=Budget When You Can’t Estimate
}}
{{WebSourceListItem
|url=http://www.infoq.com/news/2015/10/planning-noestimates
|site=InfoQ
|person=Ben Linders
|title=Planning with #NoEstimates
}}

Latest revision as of 17:13, 19 November 2017

When we praise and glorify the team working late to meet speculative estimates, we destroy life and corrupt the culture of the company.
@zenagilist
Just start referring to “estimates” as lies. “How long will that take?” “Well, if I had to lie, a week?”
@trek
Alternative to estimates: do the most important thing until either it ships or it is no longer the most important thing.
Kent Beck
In preparing for [projects] I have always found that [estimates] are useless, but [estimating] is indispensable.
General Dwight D. Eisenhower
It’s better to be roughly right than precisely wrong
Maynard Keynes

We keep on estimating and planning according to those estimates, expecting to meet deadlines and firing the wise fools that question the practice, and report the actual numbers that are not accepted by management. However…

Insanity: Doing the same thing over and over and expecting different results.
Albert Einstein
Ask, “Is the estimate useful?” rather than “Is the estimate right or wrong?”
Chris Matts

Watch out for:

Estimates become targets.
Esther Derby

Use yesterday’s weather, which implies “results from the past give guarantees for the future”.

Collect metrics about the real system, like average lead time distribution, cumulative flow diagram, average throughput, and predictability.

Thou shalt not treat estimates as commitments.

Setting deadlines and promises based on estimates is dysfunctional.

The problem with estimates isn’t so much the concept of estimates themselves—because they are fine if we know that they are estimates—but that the way we treat them in software is not like an estimate. They drive deadlines and they drive promises and because of this, we get all kinds of problems.

Sources