![Ilussive sense that we know,
so we are safe.
’Sometimes, a very inaccurate estimate
acts as a sedative: it will provide you with
bad information that will make you feel secure,
but when you realize the estimates were wrong
it might be too late […]’
Vasco Duarte
What do we
get from
estimates?](https://image.slidesharecdn.com/estimates-4devs-181023104413/85/Who-and-why-uses-estimates-talk-about-waste-4devs-8-320.jpg)
![’The Product Backlog should be a
description of the product, feature by
feature in priority order. […] And this
is a very important approach when you
want to focus on business value:
prioritization comes before estimation.
[…] My advice is simple: focus on value
first, and then figure out how to deliver
that value as quickly as possible. Don’t
estimate your way into excuses. Deliver
it, bit by bit, incrementally.’
Vasco Duarte
Planning vs.
Estimating
Planning is focused on business values
and means prioritizing.
Doesn’t treat estimates as a value itself.](https://image.slidesharecdn.com/estimates-4devs-181023104413/85/Who-and-why-uses-estimates-talk-about-waste-4devs-12-320.jpg)
Who and why uses estimates - talk about waste 4devs
- 1. Who and why uses estimates Talk about waste
- 2. What estimates really are? The Merriam-Webster Dictionary definition: ‘Estimate’ (transitive verb) as ‘to give or form a general idea about the value, size or cost of something’ Estimates are probable ammount of effort identified in hours or story points, based on experience and knowledge.
- 3. Estimates are in their nature
- 4. Stephan von Rooden about estimating: ’If you estimate a user story with a value of 8 story points and it turns out that in retrospect you would have estimated it 40 there is nothing you can do about that. The only thing you can do if you estimated something incorrect is learn from it.’
- 5. Troy Magennis about estimates: ’When we asked someone to estimate how long it will take to develop a feature or project they think about how long it would take hands-on, with PERFECT hand-off between teams and other staff with the specialist skillset. This never happens.’
- 6. For whom estimates really are? BUSINESS
- 7. Weak points of estimate approach NO PRODUCT VALUE Estimates aren’t the value itself. They are part of proccess. NO GUARANTEE IT WORKS Estimates aren’t correct information. They are just a guess. TIME CONSUMING Estimates need time to be done. Teams are spending time for nondevelopment issue.
- 8. Ilussive sense that we know, so we are safe. ’Sometimes, a very inaccurate estimate acts as a sedative: it will provide you with bad information that will make you feel secure, but when you realize the estimates were wrong it might be too late […]’ Vasco Duarte What do we get from estimates?
- 9. So the questions are… Do we want to use estimates? Do we need estimates? And the most important…
- 10. Good practices vs. known practices There is difference between good practices and well known practices. We often don’t think about practices we use, because they are habits and nobody wants to change habits. What is known is easier for our brain to use, even if it’s not efficient.
- 11. Planning Poker – good practice with bad use Possibility to focus on real hardnesses. Mostly used as an estimating tool (even if the name says PLANNING). Possibility to focus on business value.
- 12. ’The Product Backlog should be a description of the product, feature by feature in priority order. […] And this is a very important approach when you want to focus on business value: prioritization comes before estimation. […] My advice is simple: focus on value first, and then figure out how to deliver that value as quickly as possible. Don’t estimate your way into excuses. Deliver it, bit by bit, incrementally.’ Vasco Duarte Planning vs. Estimating Planning is focused on business values and means prioritizing. Doesn’t treat estimates as a value itself.
- 13. Possibility to focus on hardnesses and real effort #noestimates
- 14. #noestimates #noestimates is the proposition of estimation of least effort (least of waste) LESS RISK LESS TIME CONSUMINNG FOCUS ON VALUE MORE UNDERSTANDING MORE EFFICIENCY
- 15. What do we need to use #noestimates approach data Information about number of PBIs delivered during specific sprint data Information about specific estimates updated after the sprints end (real effort data) data Information about how much time was spent on PBI development
- 16. How can we use #noestimates? To work on BUSINESS VALUES (not abstract numbers) To optimize development process To create schedule To follow velocity To establish capacity
- 17. What is the biggest value of #noestimates approach? Business value focus Business value delivery Less time waste More focus on acceptance criteria and hardnesses No guessing, just data
- 18. https://www.linkedin.com/in/agatasobek/ Thank you for your attention!