Weitere ähnliche Inhalte Ähnlich wie Lies, damn lies, estimates (6) Kürzlich hochgeladen (20) Lies, damn lies, estimates9. ©ClaysnowLimited2014
I’ll be back
tomorrow to finish off
You’ll be in by
Christmas
That will be
fixed before we
leave
All our previous
customers are
completely satisfied
We don’t make
mistakes like other
builders
You won’t
notice we’re there
Tuesday, 15 April 14
11. ©ClaysnowLimited2014
The project status is
still green
We’re 90% done
We will deliver
with zero defects
On time, on budget
every project
It’s working in the
test environment
Integration
takes hardly any
time
Tuesday, 15 April 14
14. ©ClaysnowLimited2014
The primary purpose of an estimate is not to
predict a project’s outcome;
it is to determine whether a project’s targets
are realistic enough to allow the project
to be controlled to meet them.
Steve McConnell, Software Estimation (2006)
Tuesday, 15 April 14
15. ©ClaysnowLimited2014
6. Introduction to Estimation Techniques
7. Count, Compute, Judge
8. Calibration and Historical Data
9. Individual Expert Judgement
10. Decomposition and Recomposition
11. Estimation by Analogy
12. Proxy-Based Estimates
13. Expert Judgement in Groups
14. Software Estimation Tools
15. Use of Multiple Approaches
16. Flow of Software Estimates on a Well-
Estimated Project
17. Standardized Estimation Procedures
Part II - Fundamental Estimation Techniques
Tuesday, 15 April 14
21. ©ClaysnowLimited2014
For each of the next 10 quantitative questions,
give a lower and an upper bound,
such that you believe
with about 90% certainty that the
correct answer lies within the interval given.
This means that you should expect to guess
correctly for about 9 questions out of 10.
Laurent Bossavit, www.bossavit.com, @morendil
Tuesday, 15 April 14
33. ©ClaysnowLimited2014
1) 1847
2) 199 million
3) 115 meters
4) 20 million
5) 1486
6) 379
7) 286,000
8) 45 million hectolitres
9) 304
10) 24 thousand years
Tuesday, 15 April 14
40. ©ClaysnowLimited2014
“A boundary object is a concept in
sociology to describe information used in
different ways by different communities.
They are plastic, interpreted differently
across communities but with enough
immutable content to maintain integrity”
--Wikipedia
Estimates are Boundary Objects
Tuesday, 15 April 14
41. ©ClaysnowLimited2014
“They are weakly structured in common
use, and become strongly structured in
individual-site use. They may be abstract or
concrete.
They have different meanings in different
social worlds but their structure is common
enough to more than one world to make
them recognizable means of translation.
The creation and management of boundary
objects is key in developing and maintaining
coherence across intersecting social worlds.”
-- Leigh & Griesemer
Tuesday, 15 April 14
50. ©ClaysnowLimited2014
... these studies which have for a few years
now given rise to the claim that "research
shows that people are better at relative
than absolute estimation" do not in fact
seem to square with that claim.
This doesn't entail that relative estimation
doesn't work - only that it is not proven.
http://guide.agilealliance.org/guide/relative.html
Tuesday, 15 April 14
57. There are known knowns; there are things we
know that we know.
There are known unknowns; that is to say there
are things that, we now know we don't know.
But there are also unknown unknowns
– there are things we do not know we
don't know.
Tuesday, 15 April 14
59. ©ClaysnowLimited2014
“... during an inception, when we are
most ignorant
about most aspects of the project,
the best use
we can possibly make of the time available
is to attempt to
identify and reduce
our ignorance”
http://dannorth.net/2010/08/30/introducing-deliberate-discovery/
Deliberate discovery
Tuesday, 15 April 14
60. ©ClaysnowLimited2014
1. Just about everyone in the world has
done this.
2. Lots of people have done this, including
several people in the company.
3. Someone in our company has done this.
4. Someone in the world did this, but not in
our organisation (and probably at a
competitor).
5. Nobody has ever done this before.
http://lizkeogh.com/2013/07/21/estimating-complexity/
Estimating Complexity
Tuesday, 15 April 14
70. ©ClaysnowLimited2014
Done conventionally, software projects offer
almost no information, and almost no
control, to those who are given the
responsibility to manage them.
... the people in charge of spending money
to get software really do need control and
information.
Saying “no” doesn’t help them.
http://xprogramming.com/articles/artifacts-are-not-the-problem/
Tuesday, 15 April 14
73. ©ClaysnowLimited2014
Dear Customer
... when we start an IT project, we don’t know
how much time and effort it will take to
complete.
Consequently, we don’t know how much it will
cost.
http://www.agileconnection.com/article/dear-customer-truth-about-it-projects?page=0%2C0
Tuesday, 15 April 14
75. ©ClaysnowLimited2014
“Old fogies know
your estimates will be bogus.
They know you
won’t
get them right.
They know you
won’t
hit the deadline with
full scope”
http://xprogramming.com/articles/artifacts-are-not-the-problem/
Tuesday, 15 April 14
76. ©ClaysnowLimited2014
Challenge the use of estimates
- understand its value
Estimates are not commitments
- make this crystal clear
Is it small or just far away
- ignorance is the major constraint
Take aways
Tuesday, 15 April 14
78. Seb
Rose
Twi$er:
@sebrose
Blog:
www.claysnow.co.uk
E-‐mail:
seb@claysnow.co.uk
Tuesday, 15 April 14
79. ©ClaysnowLimited2014
Estimates produced before a project starts are lies
about how much something will cost, usually tailored
depending on whether the source of the estimate
wants the project to go ahead or not.
Estimates produced once a project has started are
lies that compensate for the inaccuracies of
earlier estimates.
Both contribute towards an illusion of control
that is no more real in software than it is in civil
engineering.
http://accu.org/index.php/journals/1836
Tuesday, 15 April 14