Food for Agile Thought’s issue #116—shared with 12,576 peers—covers agile experiments, and how to free yourself from five failure anxieties when transitioning to agile.
We also learn how to motivate people to be on time (without playing Bob Marley), and how to rebuild trust in a product and engineering team.
Lastly, we learn from Julian Birkinshaw—Professor of Strategy and Entrepreneurship at the London Business School—about Agile’s impact on strategy.
Have a great week!
Food for Agile Thought’s issue #115—shared with 12,439 peers—focuses on winning hearts and minds in the organization as we borrow from political campaigns, and we now can convince financially-minded business people about the Agile ROI.
We also go the extra mile providing transparency on the product process, we learn how to translate prioritization into numbers every MBA understands, and we kiss ‘one-size-fits-all’ Agile good-bye.
Lastly, John Cutler asks the right question: Shall the product organization focus on learning fast or shipping fast?
Have a great week!
Food for Agile Thought’s issue #114—shared with 12,308 peers—focuses on team building and rockstar engineers, or better: the lack of them. We also come back to psychological safety and wonder whether the term is overused or abused?
Steve Denning explains why SAFe == pre-Copernican command and control thinking, and we learn what misconception lets software product spiral out of control.
Lastly, Kate Bennet shares the results of her survey on product prioritization methods.
Have a great week!
Food for Agile Thought’s issue #113—shared with 12,181 peers—covers scaling Spotify, why technical debt gets out of control, how to go faster, and that customer centricity requires changes to the organization.
We also have a look at ‘Cost of Delay’ as a concept and learn that buildings MVPs might be counterproductive, and to make (product) decisions without a doubt.
Lastly, Hiten Shah considers Trello a failure—find out why.
Have a great week!
Food for Agile Thought’s issue #112—shared with 11,952 peers—focuses on scaling agile pitfalls, particularly in complex systems.
We also have a look at Sam DeBrule’s giant resource list for product and design that makes being a product mensch a bit simpler and more exciting.
Lastly, there is a new blog post available: How to up your game as a product owner. (The PO anti-patterns should be familiar with many scrum teams.)
Have a great week!
Food for Agile Thought’s issue #111—shared with 11,775 peers—dives into slicing user stories, and asks: Is becoming an agile coach the only career goal for scrum masters?
We also apply the Team Culture model to high-performing teams, analyze the scrum master role with causal loop diagrams, and bust the myth that great products result from listening to your customers.
Lastly, Ken Norton pitches the idea of having a thirty-year plan, and we learn how the Design Sprint emerged as a concept.
Have a great week!
