Food for Agile Thought’s issue #149—shared with 18,075 peers—addresses the multitasking fallacy many managers suffer from, how to design an organization that supports agile teams tasked with solving customers’ problems, and what to do when your Scrum team gets too large.
We also enjoy Marty Cagan’s follow-up post—I hope you have read ‘The Revenge of the PMO’—as well as Teressa Torres’ pitch to continuously challenge your beliefs. (Running user interviews seems to be a good starting point.)
However, what if ‘Agile’ is merely a cult, something we made up collectively that is of no importance when it comes to creating outstanding products?
Food for Agile Thought’s issue #148—shared with 17,986 peers—focuses on unagile SAFe ®, how the PMO strikes back, and whether ‘agile’ makes sense at all.
We learn from Marty Cagan that most large organization do not (yet) understand the different concepts of project-orientation vs. product-orientation. Which is a good reason to also dive into the particularities of enterprise product management.
However, there is hope: K2K managed to turn more than 70 organizations into self-organizing flourishing entities. Learn how this happened.
Food for Agile Thought’s issue #147—shared with 17,882 peers—addresses business agility and what is required to make it happen. We learn that merely scaling ‘agile’ is not the path as business agility also needs changes of a different nature. Overcoming the traditional budgeting process, for example.
Speaking of which, Steve Denning contributes ten axioms that make traditional managers anxious; ridiculing ‘agile’ is no longer an option to deal with it.
Lastly, we borrow six tips to handle demanding stakeholders without burning bridges, and we learn which low-hanging fruits to pick to make an excellent first impression as a newly hired product manager.
Food for Agile Thought’s issue #146—shared with 17,791 peers—addresses finding agile metrics, how to play the product game safe and lose, and why BDD is an integral part of business agility.
We also ask yourselves: Should an agile coach rather be an organizational psychotherapist? Or what are you doing all day if you’re supporting a single team as a scrum master?
Lastly, our gut feeling is confirmed that innovation does not happen under pressure as well as that ‘saying yes’ is not scaling technique to build successful products. (Fortunately, there are also six ways how to accomplish growth without trying to be everybody’s darling.)
Food for Agile Thought’s issue #145—shared with 17,732 peers—addresses how to make agile work for you, how graphics can massively improve your facilitation skills, and how you can identify friends and foes with an organizational design analysis.
We also get a better understanding of Kanban Cadences, how to sell and prioritize non-feature work such as refactoring, and why merely shipping code does not mean you understand the philosophy of Kaizen.
Lastly, learn new tips and trick on how to deal with HIPPOs and their pet projects in your organization.
Food for Agile Thought’s issue #144—shared with 17,591 peers—covers Mary Meeker’s epic report on Internet trends 2018, the background on why and how Amazon figured out the benefits of Amazon Prime, and why smart organizations leave the decision making to those closest to a problem.
We also appreciate Setapp’s detailed process to run product-/market fit analyses, and we learn why improving flow is the Swiss Army knife to solving all kind of issues.
Lastly, Leon Tranter makes a compelling pitch to dare more Kanban, and yes, running experiments will reduce output — if you ignore flow basics in the process.
