Here's a picture from a Tweeter post (without attribution) that is suggested to represent what it means to apply #NoEstimates
Let's look at the detail of each of the boxes in the context of the uncertainties encountered on all projects
Prioritize features and stories by Value
Priority means different things to different stakeholders. Without a clear and concise definition of the Units of Measures for those stakeholders, prioritizing the Features is just a buzzword.
For the marketing department, priority may be related to product positioning. Being able to announce this feature is coming in the spring release
Slice Features into Thin Stories
Smaller work takes a shorter time. But smaller work does not reducible Epistemic uncertainty that creates risk. Smaller work does not do anything for the Aleatory uncertainty that creates risk.
All smaller work does is make to outcomes of that work appear faster so corrective or preventive actions can be talken faster.
This is good, but it does not remove the need to estimate the impact of risk on the work. That risk - from the Reducible (Epistemic) and Irreducible (Aleatory) uncertainties is still there. It is not dealt with by smaller work.
Track Velocity as Stories Completed Per Sprint
Velocity is an ordinal number. Ordinal numbers are relative measures. Those paying for the work make their decisions based on cardinal numbers. Time and money are cardinal numbers.
Time-Box the Project and the Features
Tiem boxing is fine, IF and ONLY IF reducible risk is handled and irreducible risk has a margin
Update the Forecast Frequently
Yes, this is standard risk management. These updates must be risk adjusted. Velocity has nothing to do with risk
Risk Management is Project Management for Adults - Tim Lister
Start acting like an adult and start applying risk management and stop using ordinal measures of progress, and stop thinking the making smaller with does anything for the risk of you showing up late, over budget, and having your stuff not work.
