Food for Agile Thought #206: Breaking Hierarchy, Estimation & #noEstimates, Change Agents, 10x Experiments

Food for Agile Thought’s issue #206—shared with 23,491 peers—covers Spotify’s approach to breaking hierarchy; we revisit the estimation discussion, and we consider reasons why teams may not be interested in becoming agile.

We also learn how to 10x our experimentation capacity; we discover five machine learning lessons for product managers, and we track value in an agile transformation.

Lastly, we delve into types of agile coaches—from cargo cult to transformative.

Did you miss last week’s Food for Agile Thought’s issue #205?

Food for Agile Thought #206: Breaking Hierarchy, Estimation & #noEstimates, Change Agents, 10x Experiments

Continue reading Food for Agile Thought #206: Breaking Hierarchy, Estimation & #noEstimates, Change Agents, 10x Experiments

Liberating Structures for Scrum (4): The Daily Scrum

TL;DR: The Liberating Structures Daily Scrum Meetup

This Liberating Structures for Scrum meetup addressed the Daily Scrum, particularly the notion that it is barely possible to create a Liberating Structure Daily Scrum string that fits into the 15-minutes time-box of the Daily Scrum. Learn more on how to bust that myth.

Hands-on Agile Meetup Berlin: Liberating Structures for Scrum (4): The Daily Scrum

Continue reading Liberating Structures for Scrum (4): The Daily Scrum

Food for Agile Thought #205: Agile Principles, Agile’s Course, Amazon’s Innovation Formula, Innovation w/o Labs

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 #205: Agile Principles, Agile’s Course, Amazon’s Innovation Formula, Innovation w/o Labs

Continue reading Food for Agile Thought #205: Agile Principles, Agile’s Course, Amazon’s Innovation Formula, Innovation w/o Labs

Food for Agile Thought #204: Scrum & TPS, Strategy Knotworking, Kill Your Product Backlog, Youtube as an MVP

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 #204: Scrum & TPS, Strategy Knotworking, Kill Your Product Backlog, Youtube as an MVP

Continue reading Food for Agile Thought #204: Scrum & TPS, Strategy Knotworking, Kill Your Product Backlog, Youtube as an MVP

Scrum First Principles — How to Elon Musk the Scrum Guide

TL; DR: Scrum First Principles

Popularized by Elon Musk, utilizing first principles thinking to solve problems in an innovative, creative, and less biased way has proven popular in the tech community. Given that its sibling empiricism is an integral part of Scrum as a framework, applying Scrum first principles thinking is also a useful exercise.

Learn more about how to Elon Musk the Scrum Guide.

Scrum First Principles — Age-of-Product.com

Continue reading Scrum First Principles — How to Elon Musk the Scrum Guide

Food for Agile Thought #203: Zombie Scrum, Black Mirror Ethics, Apex Predators in Agile, How to Product Update

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 #203: Zombie Scrum, Black Mirror Ethics, Apex Predators in Agile, How to Product Update

Continue reading Food for Agile Thought #203: Zombie Scrum, Black Mirror Ethics, Apex Predators in Agile, How to Product Update