Food for Agile Thought #152: Agile Estimates, #NoEstimates, #WhyEstimates, Product Design Tools, Top-Down or What?
Food for Agile Thought’s issue #152—shared with 18,406 peers—focuses agile estimates: are they always waste or are there situations where agile estimates are useful? Moreover, in the latter case how to make sure that you provide the right estimates?
We also enjoy a sample chapter from a good book on product design, listing nine critical tools, and shed light on the questions whether infrastructure teams need product management, too.
John Cutler reflects on a personal pattern of how coaching engagements start—and end.
Ron Jeffries’ view on estimates is simple: they are always waste.
Johanna Rothman shares how to deliver the ‘right estimate’ if your organization (still) requires estimations.
John Cutler’s article lists 20 reasons why estimates may be useful in your organization.
Join me in Zurich on August 24th, 2018, for a round of the Agile Fluency Game ™.
The Agile Fluency Game ™ is designed to simulate these situations, gives room to play through these processes in different ways and helps you to make informed and conscious decisions for your organization.
Learn more: The Swiss Agile Association presents The Agile Fluency™ Game in Switzerland.
Rich Mironov: Do Infrastructure Teams Need Product Management?
Rich Mironov advocates that a development team deserves a product manager—why burden an engineer with the associated tasks?
Source: Do Infrastructure Teams Need Product Management?
Liz Love (via ProdPad): Product Management approaches: top down, bottom up or both?
Liz Love suggests pursuing a hybrid of the top down as well as the bottom-up PM strategy.
Source: ProdPad: Product Management approaches: top down, bottom up or both?
Read more: Food for Agile Thought #151: Beyond Budgeting, Open Workspace Horror, Product Vision Principles.