Food for Agile Thought’s issue #205—shared with 23,482 peers—covers agile principles; we explore the foundation of organization-wide agility, and we embrace the benefits of trunk-based development.
We also have a look at Amazon’s formula for innovation; we learn why abolishing innovation silos is beneficial, and we appreciate a comprehensive workbook on Design Thinking.
Lastly, we ask: is our industry heading for trouble?
Did you miss last week’s Food for Agile Thought’s issue #204?
Food for Agile Thought’s issue #204—shared with 23,376 peers—turns to Scrum TPS to 3-5x quality and value; we learn how to weave strings of Liberating Structures to achieve a Scrum Team’s goals, and we adjust our approach to handling organizational change.
We then kill our product backlogs; we embrace the idea of #nocode MVPs, and we come back again to the question of user story sizing.
Lastly, we ask: how come that so many agile transformations still fail, given the wealth of knowledge accumulated on the topic over recent years?
Did you miss last week’s Food for Agile Thought’s issue #203?
Food for Agile Thought’s issue #203—shared with 23,236 peers—revisits the case for a combined top-down, bottom-up approach to agile transformations; we learn how to identify and deal with Zombie Scrum, and we consider the usefulness of making a Development Team member also the Scrum Master.
We then address how to communicate product changes to customers in a way that they will not freak out; we go Black Mirror with ethic tests, and we consider how to communicate as a product mensch with engineers without making them freak out either.
Lastly, we ask whether it is futile to resist the slow but steady assimilation of coaches into an organization’s culture?
Did you miss last week’s Food for Agile Thought’s issue #202?
Food for Agile Thought’s issue #202—shared with 22,882 peers—dives into mental models and cognitive biases that impede decision making; we browse through a case study of a failed large Scrum project in the financial industry, and we get more ideas on how to overcome agile transition antibodies of an organizational immune system.
We also address how to make product discovery less of a gamble; we consider suitable metrics for an innovation program, and we get a glimpse at ProductOps. (DevOps, DesignOps, and now ProductOps—the space is getting crowded.)
Lastly, we learn more about how “Agile” is working around the globe, and how we could learn from other cultures.
Did you miss last week’s Food for Agile Thought’s issue #201?
Food for Agile Thought’s issue #201—shared with 22,612 peers—delves into software nature, we correct some popular misconceptions about Scrum, and we revisit the idea that innovation always includes failure, and that teams should experience it safely.
We also address the conceptual difference of product management for machine learning compared to ‘normal’ product management; we embrace the importance of disrupting ourselves, and we appreciate the Product Backlog ordering quadrant.
Lastly, we learn how to help teams that do not want to be coached.
Did you miss last week’s Food for Agile Thought’s issue #200?
Food for Agile Thought’s issue #200—shared with 22,519 peers—delves into fixed agile, we learn about how large organizations assess a Scrum Master’s qualification, and why ‘agile transformation’ is not ideal as a story to tell.
We also ask whether all of your organization’s members can answer the “what is your product” question consistently, we gain a better understanding how uncertainty will influence product discovery and delivery, respectively, and brush up our understanding of effective Product Backlog refinement techniques.
Lastly, we like to thank Basecamp for providing another free webbook on software project management Basecamp-style. (#NoAgile, #NoScrum, #NoWaterfall, #NoPostits, #NoSprints, #NoStandups — just saying.)
Did you miss last week’s Food for Agile Thought’s issue #199?
