After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendations the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
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.
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?
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.
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.
