TL; DR: Agile’s Demise, Big Scale Digital Transformations—Food for Agile Thought #232
Welcome to the 232nd edition of the Food for Agile Thought newsletter, shared with 25,623 peers. This week, we look back at ‘Agile’ and ask yourselves: Are the rumors of its demise exaggerated? We also get the inside view of a large scale digital transition of a traditional engineering corporation.
We then explore the perils of being probably too data-driven; we learn how to drive innovation from Mr. Business Model Canvas, and we take ten essential rules of team objectives to heart.
Lastly, we sharpen our tools to overcome any disengagement of team members and continue our Scrum anti-patterns series, focusing on stakeholders.
TL; DR: Liberating Structures, Beautiful Mess—Food for Agile Thought #231
Welcome to the 231st edition of the Food for Agile Thought newsletter, shared with 25,467 peers. This week, we learn about Liberating Structures and change for everyone; we point at the perils of measuring a complex reality, and we get a better understanding of where business agility is heading.
We also enjoy John Cutler’s excursion into embracing change successfully; we gain insight into three ways of making decisions in complex situations, and we listen to why OKRs may not provide the right objectives for a product team.
Lastly, we look back at the evolution of Haier’s organizational model and how self-organization and refrigerators go hand-in-hand.
TL; DR: Kent Beck, Psychological Safety—Food for Agile Thought #230
Welcome to the 230th edition of the Food for Agile Thought newsletter, shared with 25,326 peers. This week, we listen to Kent Beck, the XP creator; we get into the details of how agile leadership manifests itself, and we follow Dave Snowden analyzing a three-part-question popularized by Liberating Structures.
We also delve into the top ten deliverables of product managers; we embrace new ways of organizing our Product Backlogs, and we enjoy the deep-dive into the benefits of the north star framework.
Lastly, we ask what ‘psychological safety’ actually means in practice.
TL; DR: Traumatic Agile, Absurd Design Sprints—Food for Agile Thought #229
Welcome to the 229th edition of the Food for Agile Thought newsletter, shared with 25,103 peers. This week, we ask whether ‘Agile’ is a reactionary movement; we delve into suitable metrics for experiments, and we learn from a bank how to become agile with 20-plus teams.
We also learn how Pinterest keeps ideas for experiments coming. Speaking of which, we gain insight into suitable experiments at Slack, and we reconsider the usefulness of Design Sprints.
Lastly, we finally have a reference to answer the obvious question: Does Google use Scrum?
TL; DR: Asking Good Questions, Trade-offs & Debts—Food for Agile Thought #228
Welcome to the 228th edition of the Food for Agile Thought newsletter, shared with 25,103 peers. This week, we delve into asking good questions, thus overcoming assumptions; we learn more about the cognitive science behind ‘Agile,’ and we cautiously check SAFe again.
We gain insight into how to handle product failures catastrophes; we reflect whether trade-offs are worth the costs. Also, we come back to defining what a product is, focusing on its two critical elements.
Lastly, we appreciate an excursion into psychological safety—from its origins to pioneering its application.
TL; DR: Agile Core Beliefs, Psychology of Feature Adoption—Food for Agile Thought #227
Welcome to the 227th edition of the Food for Agile Thought newsletter, shared with 25,021 peers. This week, we address agile core beliefs; we embrace the idea of a one-day Sprint, and we come back to agile coaching competencies.
We also learn how to move on as a product team, struggling with becoming data-informed; we explore cognitive biases in the adoption progress of new features, and we figure out how to speed up A/b tests without sacrificing accuracy.
Lastly, we appreciate the notion that we are not all designers—despite stickies, sharpie, and prototyping apps.
