Three Essential Agile Failure Patterns in 7:31 Minutes—Making Your Scrum Work #12

TL; DR: Essential Agile Failure Patterns — When Noise Interferes with Signal

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. When Scrum becomes an element of an agile transformation, the following three common essential agile failure patterns prove to be an exceptionally tough nut to crack for any Scrum Master.

📺 Join me and explore the consequences of foreseeable failure patterns and what you can do about them in a little more than seven minutes.

Three Essential Agile Failure Patterns in 7:31 Minutes—Making Your Scrum Work #12 — Age-of-Product.com

Update: I am running a poll on LinkedIn—join the voting: “What is your top agile failure pattern in organizations?”

Continue reading Three Essential Agile Failure Patterns in 7:31 Minutes—Making Your Scrum Work #12

Food for Agile Thought #295: Overcoming Team Limits, Pharma Success Story w/ Scrum, The Mediocrity Trap, Your Product is Not Their Problem

TL; DR: Overcoming Team Limits, The Mediocrity Trap—Food for Agile Thought #295

Welcome to the 295th edition of the Food for Agile Thought newsletter, shared with 31,527 peers. This week, we delve into overcoming team limits with Jeff Sutherland, the co-creator of Scrum. We also dive into an adjacent topic: Team-building in organizations that double the employee count at least yearly, and we analyze some psychological issues that might interfere with the core of agility.

We then share ten compelling reasons why to stay out of meh work. Moreover, we reflect on the necessity of loving your customer’s problem, not your solution, and we embrace a comprehensive primer on how innovators can use the JTBD framework to create successful products.

Lastly, we appreciate a new academic paper on the effectiveness of Scrum teams.

Food for Agile Thought #295: Overcoming Team Limits, Pharma Success Story w/ Scrum, The Mediocrity Trap, Your Product is Not Their Problem — Age-of-Product.com
Continue reading Food for Agile Thought #295: Overcoming Team Limits, Pharma Success Story w/ Scrum, The Mediocrity Trap, Your Product is Not Their Problem

The Oversized Product Backlog Will Cost You Dearly — Making Your Scrum Work #11

TL; DR: The Oversized Product Backlog Problem — When Noise Interferes with Signal

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. Neglecting the critical Scrum artifact for continuous value creation is one of the common Scrum anti-patterns. If your Scrum Team strives to make your customers’ lives easier Sprint after Sprint, beware of the oversized Product Backlog.

📺 Join me and explore the consequences of inadequate Product Backlog management in less than three minutes.

The Oversized Product Backlog Problem — Making Your Scrum Work #11 — Age-of-Product.com

Update: I am running a poll on LinkedIn—join the voting: “What reasons have you observed why Scrum Teams stuff their Product Backlogs — a very costly pattern that diminishes ROI and value creation?”

Continue reading The Oversized Product Backlog Will Cost You Dearly — Making Your Scrum Work #11

Food for Agile Thought #294: The Spotify Model Fallacy, Pirates & Leadership, Building Stuff to Close Deals, Scheduling Innovation?

TL; DR: Spotify Model Fallacy, Pirates & Leadership—Food for Agile Thought #294

Welcome to the 294th edition of the Food for Agile Thought newsletter, shared with 31,412 peers. This week, we dissect the Spotify model fallacy. (By the way, Spotify is no longer using product squads.) We also point at the forward-thinking approach of pirates regarding governance and self-management and why some people have difficulties embracing the idea of autonomous action by self-directed individuals.

We then learn the two only ways of pushing back requests to build features to close deals. Moreover, we list core principles that come with experimentation and what it takes to drive the change; finally, we analyze the popular leadership fallacy to mandate creating ‘innovative feature,’ probably, with a timeline, incentivized by OKRs.

Lastly, we delve into the origins of feature creep, adding on top of the usual suspects—such as gold-plating—the difficulties that distributed teams face. (See also Gold-Plating Beyond Done — Making Your Scrum Work #7.)

Food for Agile Thought #294: The Spotify Model Fallacy, Pirates & Leadership, Building Stuff to Close Deals, Scheduling Innovation? — Age-of-Product.com
Continue reading Food for Agile Thought #294: The Spotify Model Fallacy, Pirates & Leadership, Building Stuff to Close Deals, Scheduling Innovation?

The Frustrated Scrum Master — When all the Effort Leads Nowhere

TL; DR: The Frustrated Scrum Master — When all the Effort Leads Nowhere

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. One failure symptom of a botched agile transformation is the frustrated Scrum Master.

📺 Join me and explore the consequences of a Scrum Master who has thrown in the towel in 92 seconds.

The Frustrated Scrum Master — When all the Effort Leads Nowhere — Age-of-Product.com
Continue reading The Frustrated Scrum Master — When all the Effort Leads Nowhere

Why Scrum Requires a Failure Culture — Making Your Scrum Work #10

TL; DR: Scrum Failure Culture: A Requirement to Be Successful

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. To make things worse, a crucial success factor of every Scrum team is not even mentioned in the Scrum Guide: Any organization that wants to employ Scrum to learn faster than its competitors needs to have a solid failure culture.

📺 Join me and explore the consequences of not living a failure culture in less than three minutes.

Scrum Failure Culture: A Requirement — Making Your Scrum Work #11 — Age-of-Product.com
Continue reading Why Scrum Requires a Failure Culture — Making Your Scrum Work #10