Doesn't deemphasizing estimates acknowledge and imply that the estimate is delivering whatever the boss (I mean, Product Owner) wants, when they want it? Possibly with the ineffective filter of bullying and misleading the team into some imprudent commitment instead of simply ordering?<p>For example, between 2011 and 2020 the Product Backlog items lost the estimate: it means that if that feature is late it is the fault of a struggling developer, not of a superficial planner.
> It no longer has remnants of output thinking and firmly underlined the importance of outcome thinking.<p>As far as I can see the article doesn't define these terms. Does anyone know what they mean in this context? Aren't "output" and "outcome" just two words for the same thing within the context of a software project to implement a feature or make a change?
Should be: Removed from the Scrum <i>guide</i>. Most places are still happily using story points as a form of measuring time.<p>Doesn't really matter what the book says when both places and consultants en masse say it is B and not A.