2. JAREK RATAJSKI
JAREK RATAJSKI
JAREK RATAJSKI
Software Developer at Digital Asset
Software Developer at Digital Asset
Software Developer at Digital Asset
3. The talk is based on my personal opinions and
The talk is based on my personal opinions and
The talk is based on my personal opinions and
does not represent point of view of my
does not represent point of view of my
does not represent point of view of my
company or customers I am working for
company or customers I am working for
company or customers I am working for
5. Actually, there is no evidence such experiment
Actually, there is no evidence such experiment
Actually, there is no evidence such experiment
was ever held
was ever held
was ever held
6. Some scientists claim that monkeys are not
Some scientists claim that monkeys are not
Some scientists claim that monkeys are not
that stupid
that stupid
that stupid
13. What is an
What is an
What is an estimation
estimation
estimation?
?
?
14. Estimation
Estimation
Estimation (or estimating) is the process of
(or estimating) is the process of
(or estimating) is the process of
finding an estimate, or approximation, which is
finding an estimate, or approximation, which is
finding an estimate, or approximation, which is
a value that is usable for some purpose even if
a value that is usable for some purpose even if
a value that is usable for some purpose even if
input data may be
input data may be
input data may be incomplete
incomplete
incomplete,,
, uncertain
uncertain
uncertain, or
, or
, or
unstable
unstable
unstable..
.
https://en.wikipedia.org/wiki/Estimation
https://en.wikipedia.org/wiki/Estimation
https://en.wikipedia.org/wiki/Estimation
15. What is an
What is an
What is an estimator
estimator
estimator?
?
?
16. An "estimator" or "point estimate" is a statistic
An "estimator" or "point estimate" is a statistic
An "estimator" or "point estimate" is a statistic
(that is, a function of the data)
(that is, a function of the data)
(that is, a function of the data)
https://en.wikipedia.org/wiki/Estimator
https://en.wikipedia.org/wiki/Estimator
https://en.wikipedia.org/wiki/Estimator
17. An "estimator" or "point estimate" is a statistic
An "estimator" or "point estimate" is a statistic
An "estimator" or "point estimate" is a statistic
(that is, a function of the data)
(that is, a function of the data)
(that is, a function of the data)
the estimator is itself a random(!) variable
the estimator is itself a random(!) variable
the estimator is itself a random(!) variable
https://en.wikipedia.org/wiki/Estimator
https://en.wikipedia.org/wiki/Estimator
https://en.wikipedia.org/wiki/Estimator
19. TRUE ANSWER:
TRUE ANSWER:
TRUE ANSWER:
Estimation is a process of keeping software
Estimation is a process of keeping software
Estimation is a process of keeping software
developers frustrated
developers frustrated
developers frustrated
20. TRUE ANSWER:
TRUE ANSWER:
TRUE ANSWER:
Estimation is a process of keeping software
Estimation is a process of keeping software
Estimation is a process of keeping software
developers frustrated
developers frustrated
developers frustrated
21. TRUE ANSWER:
TRUE ANSWER:
TRUE ANSWER:
Estimation is a process of keeping software
Estimation is a process of keeping software
Estimation is a process of keeping software
developers frustrated
developers frustrated
developers frustrated
Agile Developers
Agile Developers
Agile Developers
22. if someone needs perfect estimates?
if someone needs perfect estimates?
if someone needs perfect estimates?
23.
24. This is the only sure method
This is the only sure method
This is the only sure method
26. Why do estimations work for the construction
Why do estimations work for the construction
Why do estimations work for the construction
industry
industry
industry
27. Why do estimations work for the construction
Why do estimations work for the construction
Why do estimations work for the construction
industry
industry
industry
‒ but not in IT?
‒ but not in IT?
‒ but not in IT?
29. You have tools, materials, specialists with
You have tools, materials, specialists with
You have tools, materials, specialists with
experience in exactly that tools
experience in exactly that tools
experience in exactly that tools
‒ You have known tools and materials
‒ You have known tools and materials
‒ You have known tools and materials
30. You have tools, materials, specialists with
You have tools, materials, specialists with
You have tools, materials, specialists with
experience in exactly that tools
experience in exactly that tools
experience in exactly that tools
‒ You have known tools and materials
‒ You have known tools and materials
‒ You have known tools and materials
‒ You have specialists with experience in
‒ You have specialists with experience in
‒ You have specialists with experience in
exactly that tool set
exactly that tool set
exactly that tool set
31. You have tools, materials, specialists with
You have tools, materials, specialists with
You have tools, materials, specialists with
experience in exactly that tools
experience in exactly that tools
experience in exactly that tools
‒ You have known tools and materials
‒ You have known tools and materials
‒ You have known tools and materials
‒ You have specialists with experience in
‒ You have specialists with experience in
‒ You have specialists with experience in
exactly that tool set
exactly that tool set
exactly that tool set
‒ Tasks are often repetitive/standarized
‒ Tasks are often repetitive/standarized
‒ Tasks are often repetitive/standarized
32. In software development
In software development
In software development we do not repeat
we do not repeat
we do not repeat
33. We can
We can
We can
but it would be slow
but it would be slow
but it would be slow
34. We are building our tools and changing our
We are building our tools and changing our
We are building our tools and changing our
materials while we work with them
materials while we work with them
materials while we work with them
This makes us elastic, powerful
This makes us elastic, powerful
This makes us elastic, powerful
but makes software development less
but makes software development less
but makes software development less
predictable
predictable
predictable
35.
36. In IT we change plans while we are still
In IT we change plans while we are still
In IT we change plans while we are still
constructing the foundation
constructing the foundation
constructing the foundation
37. Announcement Deadline
5 September 2006 (original) 30 October 2011
25 June 2010 3 June 2012
7 May 2012 17 March 2013
27 October 2012 27 October 2013
January 2013 on/after 2014
8 January 2014 on/after 2015
24 February 2014 on/after 2016
14 May 2014 on/after 2017
December 2014 2nd half of 2017
21 January 2017 2018
15 December 2017 October 2020
38. BERLIN BRANDENBURG AIRPORT
BERLIN BRANDENBURG AIRPORT
BERLIN BRANDENBURG AIRPORT
By 2009 the construction cost was budgeted at
By 2009 the construction cost was budgeted at
By 2009 the construction cost was budgeted at
€2.83 billion
€2.83 billion
€2.83 billion
By late 2012 expenditures for Berlin
By late 2012 expenditures for Berlin
By late 2012 expenditures for Berlin
Brandenburg Airport totalled at €4.3 billion,
Brandenburg Airport totalled at €4.3 billion,
Brandenburg Airport totalled at €4.3 billion,
nearly twice the originally anticipated figure
nearly twice the originally anticipated figure
nearly twice the originally anticipated figure
39. BERLIN BRANDENBURG AIRPORT
BERLIN BRANDENBURG AIRPORT
BERLIN BRANDENBURG AIRPORT
By 2009 the construction cost was budgeted at
By 2009 the construction cost was budgeted at
By 2009 the construction cost was budgeted at
€2.83 billion
€2.83 billion
€2.83 billion
By late 2012 expenditures for Berlin
By late 2012 expenditures for Berlin
By late 2012 expenditures for Berlin
Brandenburg Airport totalled at €4.3 billion,
Brandenburg Airport totalled at €4.3 billion,
Brandenburg Airport totalled at €4.3 billion,
nearly twice the originally anticipated figure
nearly twice the originally anticipated figure
nearly twice the originally anticipated figure
2019 €9.4 billion
2019 €9.4 billion
2019 €9.4 billion (wikipedia)
(wikipedia)
(wikipedia)
45. When was the last time you estimated
When was the last time you estimated
When was the last time you estimated
something?
something?
something?
46. When was the last time you estimated
When was the last time you estimated
When was the last time you estimated
something?
something?
something?
What wrong would happen if it took 3x longer?
What wrong would happen if it took 3x longer?
What wrong would happen if it took 3x longer?
47. When do we need to estimate?
When do we need to estimate?
When do we need to estimate?
48. Fixed price projects!
Fixed price projects!
Fixed price projects!
Budgeting,
Budgeting,
Budgeting,
Feasibility study
Feasibility study
Feasibility study
49. When do we do it?
When do we do it?
When do we do it?
50. When do we do it?
When do we do it?
When do we do it?
probably too often
probably too often
probably too often
51. Does it really matter if it is 3 or 5 ?
Does it really matter if it is 3 or 5 ?
Does it really matter if it is 3 or 5 ?
52. 8 people discuss for a 30 minutes if story is
8 people discuss for a 30 minutes if story is
8 people discuss for a 30 minutes if story is
(probably)
(probably)
(probably)
1 or rather 2 days long
1 or rather 2 days long
1 or rather 2 days long
53. Everyday hundreds of developers are spending
Everyday hundreds of developers are spending
Everyday hundreds of developers are spending
time on planing ...
time on planing ...
time on planing ...
54. Everyday hundreds of developers are spending
Everyday hundreds of developers are spending
Everyday hundreds of developers are spending
time on planing ...
time on planing ...
time on planing ...
doing estimates, that are not needed
doing estimates, that are not needed
doing estimates, that are not needed
55. Or at least, that do not have to be
Or at least, that do not have to be
Or at least, that do not have to be that
that
that precise
precise
precise
57. TRUE ANSWER
TRUE ANSWER
TRUE ANSWER
The only result of having tons of estimates is
The only result of having tons of estimates is
The only result of having tons of estimates is
the possibility to play scrum tetris
the possibility to play scrum tetris
the possibility to play scrum tetris
58. TRUE ANSWER
TRUE ANSWER
TRUE ANSWER
The only result of having tons of estimates is
The only result of having tons of estimates is
The only result of having tons of estimates is
the possibility to play scrum tetris
the possibility to play scrum tetris
the possibility to play scrum tetris
59. And we play tetris to have better
And we play tetris to have better
And we play tetris to have better velocity
velocity
velocity
64. It is unit of time - just indirect
It is unit of time - just indirect
It is unit of time - just indirect
65.
66. ANSWER
ANSWER
ANSWER
An hour has approximately 60 minutes
An hour has approximately 60 minutes
An hour has approximately 60 minutes
67. TRUE ANSWER
TRUE ANSWER
TRUE ANSWER
In a real software project an hour has
In a real software project an hour has
In a real software project an hour has
approximately 20 minutes
approximately 20 minutes
approximately 20 minutes
73. DEVELOPER ANSWER
DEVELOPER ANSWER
DEVELOPER ANSWER
We do not have time for quality
We do not have time for quality
We do not have time for quality
The greatest lie of software developers
The greatest lie of software developers
The greatest lie of software developers
74. I can do it in 3 days, but I will need 6 days to do it
I can do it in 3 days, but I will need 6 days to do it
I can do it in 3 days, but I will need 6 days to do it
in a good quality with tests, reviews etc.
in a good quality with tests, reviews etc.
in a good quality with tests, reviews etc.
76. I can do it in 6 days
I can do it in 6 days
I can do it in 6 days
If needed I can do it dirty way in 3 days,
If needed I can do it dirty way in 3 days,
If needed I can do it dirty way in 3 days,
we will pay the price later
we will pay the price later
we will pay the price later
77. Do not assume business wants always quick
Do not assume business wants always quick
Do not assume business wants always quick
and dirty
and dirty
and dirty
78. Do not assume business wants always quick
Do not assume business wants always quick
Do not assume business wants always quick
and dirty
and dirty
and dirty
79. If they already have a working production ...
If they already have a working production ...
If they already have a working production ...
probably
probably
probably not
not
not
80. If this is a startup, or a new project / proof of
If this is a startup, or a new project / proof of
If this is a startup, or a new project / proof of
concept, possibly
concept, possibly
concept, possibly yes
yes
yes
83. TRUE ANSWER
TRUE ANSWER
TRUE ANSWER
Using calculated words / sentences can shift
Using calculated words / sentences can shift
Using calculated words / sentences can shift
blame for subpar code onto management
blame for subpar code onto management
blame for subpar code onto management
86. ANSWER
ANSWER
ANSWER
In sprints
In sprints
In sprints
Just run 100 meters as fast as possible
Just run 100 meters as fast as possible
Just run 100 meters as fast as possible
and repeat
and repeat
and repeat
87. Ideal sprint:
Ideal sprint:
Ideal sprint:
1st day of sprint - recovering after last sprint,
planning, retro
2-3rd day of sprint - patching worst bugs,
leftovers
4-5th day - clarifying stories
88. 6-7th day - production dramas, firefighting,
8th day - implementing stories
9th neglecting tests, reviews - because demo
10th day demo
92. ANSWER
ANSWER
ANSWER
Burndown ... It is internal
Burndown ... It is internal
Burndown ... It is internal
tool/visualsation that team uses to
tool/visualsation that team uses to
tool/visualsation that team uses to
predict delivery of sprint backlog
predict delivery of sprint backlog
predict delivery of sprint backlog
93. ANSWER
ANSWER
ANSWER
Burndown ... It is internal
Burndown ... It is internal
Burndown ... It is internal
tool/visualsation that team uses to
tool/visualsation that team uses to
tool/visualsation that team uses to
predict delivery of sprint backlog
predict delivery of sprint backlog
predict delivery of sprint backlog
Really?
Really?
Really?
98. We have:
We have:
We have:
daily
small teams
short sprints
And we need an additional chart to see how
And we need an additional chart to see how
And we need an additional chart to see how
are we progressing?
are we progressing?
are we progressing?
99. We have:
We have:
We have:
daily
small teams
short sprints
And we need an additional chart to see how
And we need an additional chart to see how
And we need an additional chart to see how
are we progressing?
are we progressing?
are we progressing?
100. TRUE ANSWER
TRUE ANSWER
TRUE ANSWER
Burndown chart is a picture that makes you
Burndown chart is a picture that makes you
Burndown chart is a picture that makes you
feel bad
feel bad
feel bad
101. Are we not getting into a big distraction?
Are we not getting into a big distraction?
Are we not getting into a big distraction?
103. Velocity somehow became
Velocity somehow became
Velocity somehow became the goal
the goal
the goal
Perfect estimates became the goal
Perfect estimates became the goal
Perfect estimates became the goal
104. Velocity somehow became
Velocity somehow became
Velocity somehow became the goal
the goal
the goal
Perfect estimates became the goal
Perfect estimates became the goal
Perfect estimates became the goal
Nice charts became the goal
Nice charts became the goal
Nice charts became the goal
105. Velocity somehow became
Velocity somehow became
Velocity somehow became the goal
the goal
the goal
Perfect estimates became the goal
Perfect estimates became the goal
Perfect estimates became the goal
Nice charts became the goal
Nice charts became the goal
Nice charts became the goal
SCRUM became the goal
SCRUM became the goal
SCRUM became the goal
108. What about?
What about?
What about?
Quality...
Quality...
Quality...
User experience...
User experience...
User experience...
109. What about?
What about?
What about?
Quality...
Quality...
Quality...
User experience...
User experience...
User experience...
Maintainability...
Maintainability...
Maintainability...
110. What about?
What about?
What about?
Quality...
Quality...
Quality...
User experience...
User experience...
User experience...
Maintainability...
Maintainability...
Maintainability...
Knowledge management...
Knowledge management...
Knowledge management...
111. What about?
What about?
What about?
Quality...
Quality...
Quality...
User experience...
User experience...
User experience...
Maintainability...
Maintainability...
Maintainability...
Knowledge management...
Knowledge management...
Knowledge management...
Developer joy
Developer joy
Developer joy
112. There are lots of strange things happening
There are lots of strange things happening
There are lots of strange things happening
around SCRUM
around SCRUM
around SCRUM
113. “The word 'agile' has been subverted to the
“The word 'agile' has been subverted to the
“The word 'agile' has been subverted to the
point where it is effectively meaningless, and
point where it is effectively meaningless, and
point where it is effectively meaningless, and
what passes for an agile community seems to
what passes for an agile community seems to
what passes for an agile community seems to
be largely an arena for consultants and
be largely an arena for consultants and
be largely an arena for consultants and
vendors to hawk services and products.” Dave
vendors to hawk services and products.” Dave
vendors to hawk services and products.” Dave
Thomas, another Manifesto signatory:
Thomas, another Manifesto signatory:
Thomas, another Manifesto signatory:
https://pragdave.me/blog/2014/03/04/time-to-
https://pragdave.me/blog/2014/03/04/time-to-
https://pragdave.me/blog/2014/03/04/time-to-
kill-agile.html
kill-agile.html
kill-agile.html
115. A personal secret. I was coding with a team
A personal secret. I was coding with a team
A personal secret. I was coding with a team
already in 199x
already in 199x
already in 199x
116. ANSWER
ANSWER
ANSWER
We were not doing any waterfall in 199x...
We were not doing any waterfall in 199x...
We were not doing any waterfall in 199x...
117. Winston Walker Royce 1970
Winston Walker Royce 1970
Winston Walker Royce 1970
... implementation described above is risky and
... implementation described above is risky and
... implementation described above is risky and
prone to failure...
prone to failure...
prone to failure...
120. Waterfall was created as a good
Waterfall was created as a good
Waterfall was created as a good public enemy
public enemy
public enemy
by agile proponents
by agile proponents
by agile proponents
129. 25% of time is sometimes 90% of energy
25% of time is sometimes 90% of energy
25% of time is sometimes 90% of energy
130. Richard Marmorstein (blog)
Richard Marmorstein (blog)
Richard Marmorstein (blog)
The critical resource is not
The critical resource is not
The critical resource is not
developer time
developer time
developer time, it's
, it's
, it's developer
developer
developer
energy
energy
energy
131. Regarding the discovery of an approach that
Regarding the discovery of an approach that
Regarding the discovery of an approach that
effectively utilizes the potential of software
effectively utilizes the potential of software
effectively utilizes the potential of software
developers
developers
developers
132. Regarding the discovery of an approach that
Regarding the discovery of an approach that
Regarding the discovery of an approach that
effectively utilizes the potential of software
effectively utilizes the potential of software
effectively utilizes the potential of software
developers
developers
developers
Exercise for the listener!!!
Exercise for the listener!!!
Exercise for the listener!!!
133. Regarding the discovery of an approach that
Regarding the discovery of an approach that
Regarding the discovery of an approach that
effectively utilizes the potential of software
effectively utilizes the potential of software
effectively utilizes the potential of software
developers
developers
developers
Exercise for the listener!!!
Exercise for the listener!!!
Exercise for the listener!!!
Q & A
Q & A
Q & A