NoEstimates

#NoEstimates

[NoEstimates @No_Estimates]

If you assigned 1 story point to every story, how much slicing would you do before you were confident you could actually complete each story in a day or so? Congratulations! You just discovered #NoEstimates. Stop trying to fit the estimate to the story. Start slicing the stories.

[NoEstimates @No_Estimates]

@erichbuhler While the neuroscience behind estimation is interesting, the cognitive and social benefits aren't exclusive to traditional practices. #NoEstimates achieves the same benefits without the antipatterns of traditional estimation.

[Vasco Duarte @duarte_vasco]

It's a well know fact that meteorology (science of weather) can scarcely forecast more than 5 days of weather ahead. Yet, software projects (which are also affected by the weather!) pretend they can plan in detail several months ahead. #noestimates

[NoEstimates @No_Estimates]

@davefarley77 Scheduling and budgeting is a management problem, not a development problem.

[Tim Ottinger @tottinge]

"It's hard to predict what this dice will roll."
"Well, then, you need to get better at predicting."

Conventional wisdom about software development processes - that unpredictable work needs better estimates, not a more predictable way of working.

[NoEstimates @No_Estimates]

@carlvellotti Stop trying to guess how big a story is. Estimate all stories as 1 point. If the team isn't 100% confident that it's 1 point, split it. Then prioritize stories by value each iteration.

If a story took longer than expected discuss as a team to understand why.

[NoEstimates @No_Estimates]

@jeffmignon @allenholub Those weren't agile teams.

[NoEstimates @No_Estimates]

@alexbunardzic Perverse incentives for the win.

[NoEstimates @No_Estimates]

@SteveTwips Then there's the engineering measure of efficiency: units of useful output per unit of input.

[NoEstimates @No_Estimates]

Guaranteed it won't be anyone with "manager" or "director" in their title.

[Vasco Duarte @duarte_vasco]

A clear example why Estimates are useless at best, and extremely unfair at worst.
Guess who gets blamed for these situations?
#noestimates

[NoEstimates @No_Estimates]

@davefarley77 Estimates

[NoEstimates @No_Estimates]

A common criticism of #NoEstimates is that the term is misleading. It's not without merit. Given its emphasis on empirical evidence over expert opinion here are just a few terms that would be more accurate:

Evidence-Based Estimation
Performance-Driven Planning
Adaptive Planning

[NoEstimates @No_Estimates]

@gregyoung Now I'm hungry. It's a conspiracy I tell ya.

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Any management that wants you to give them predictions so they can plan is living in la-la land. That's the opposite of agility. Slapping agile-ish words on waterfall does not give you agility.

[NoEstimates @No_Estimates]

@PeterKretzman @tastapod @allenholub @EzProgramming @markjgardner @jamesshore To be fair, your engagements with those movements are usually disingenuous and condescending.

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

Why do ppl assume that estimates are necessary? I don't see the need for them myself. They're solid waterfall thinking—big upfront plans, milestones, months-long delivery cycles. Not much agility. It's deployable right now. It will be deployable w/ this new capability tomorrow.

[NoEstimates @No_Estimates]

@duarte_vasco A mother's wisdom applies... Don't make promises you can't keep.

[NoEstimates @No_Estimates]

Why Effort Estimation Doesn't Work: A Comprehensive Review of Late and Over Budget Projects

[Madza 👨‍💻⚡ @madzadev]

Give this book a coding-related title 👇👇

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

@lukehohmann @stephanie_leue An estimate is not a commitment. Period.