When the Management Ignores Self-Management — Making Your Scrum Work #16

TL; DR: Ignoring Self-Management — Undermining Scrum from the Start

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 of Scrum’s first principles is self-management. It is based on the idea that the people closest to a problem are best suited to find a solution. Therefore, the task of the management is not to tell people what to do when and how. Instead, its job is to provide the guardrails, the constraints within which a Scrum team identifies the best possible solution. Join me and explore the consequences of management ignoring self-management and what you can do about it.

Ignoring Self-Management — Making Your Scrum Work #16 — Age-of-Product.com
Continue reading When the Management Ignores Self-Management — Making Your Scrum Work #16

Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14

TL; DR: Common Developer Blunders — When Your Scrum Team Lacks Alignment

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. While it is common to first look outside our team for impediments, such as dysfunctional processes or other systemic issues, I would advise starting with the Scrum team’s way of collaboration: Are we aligned on the why, what, and how? Otherwise, the three following Developer blunders may diminish the team effectiveness.

📺 Join me and explore the consequences of these Scrum Developer blunders and what you can do about them in a little more than five minutes.

Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14 — Age-of-Product.com

Update: I am running a poll on LinkedIn—join the voting: “What common ways have you observed how Developers diminish the value creation of their own work?”

Continue reading Three Common Developer Blunders in 5:05 Minutes—Making Your Scrum Work #14

When the Scrum Master Fails by Being Overly Protective — Making Your Scrum Work #13

TL; DR: When Scrum Masters Fail — Making Your Scrum Work #13

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. Scrum thrives when the Scrum teams are self-managing while Scrum Masters embrace their role as servant-leaders. However, this also implies that Scrum Masters fail when they are overly protective.

📺 Join me and explore the consequences of the overly protective Scrum Master and what you can do about it in less than three minutes.

When the Scrum Master Fails by Being Overly Protective  — Making Your Scrum Work #13 — Age-of-Product.com

Update: I am running a poll on LinkedIn—join the voting: “How can Scrum Masters fail their team by being overly protective or supportive?”

Continue reading When the Scrum Master Fails by Being Overly Protective — Making Your Scrum Work #13

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

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

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