The Dogmatic Scrum Master Anti-Pattern — Making Your Scrum Work #20

TL; DR: The Dogmatic Scrum Master Anti-Pattern

There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, how do we communicate with members of the Scrum team that take the Scrum Guide literally? What about a dogmatic Scrum Master?

Join me and delve into the effects of Scrum dogmatism in less than 120 seconds.

The Dogmatic Scrum Master? — Making Your Scrum Work #20 — Age-of-Product.com
Continue reading The Dogmatic Scrum Master Anti-Pattern — Making Your Scrum Work #20

Should Managers Attend Retrospectives? — Making Your Scrum Work #19

TL; DR: Should Managers Attend Retrospectives?

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. A classic discussion is whether it is appropriate that (line) managers attend the Retrospectives of the Scrum team. Probably, making their attendance a regular habit—or even a requirement—is not a good idea. However, what about managers that occasionally attend a Retrospective? Moreover, what if the (line) manager is also a team member?

Join me and delve into the how and when of managers attending Retrospectives in less than two minutes.

Should Managers Attend Retrospectives? — Making Your Scrum Work #19 — Age-of-Product.com
Continue reading Should Managers Attend Retrospectives? — Making Your Scrum Work #19

UnSMART Improvements at Retrospectives — Making Your Scrum Work #18

TL; DR: Unsmart Improvements

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 area that typically flies under the radar is improvements. While the Scrum Guide encourages addressing the most impactful ones as soon as possible, it is up to the Scrum team to figure out how to improve. One manifestation of this core team task we often encounter is picking unsmart improvements, though.

Join me and delve into the consequences of picking unsmart improvements as a Scrum Team in less than 90 seconds.

Unsmart Improvements — Making Your Scrum Work #18 — Age-of-Product.com
Continue reading UnSMART Improvements at Retrospectives — Making Your Scrum Work #18

Skipping Retrospectives? — Making Your Scrum Work #17

TL; DR: Skipping Retrospectives?

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 area where Scrum’s nature of being intentionally incomplete causes issues regularly is whether Scrum teams shall stick to the event schedule even if the team’s life is uneventful? For example, is skipping Retrospectives okay?

Join me and delve into the consequences of skipping Retrospectives in less than 90 seconds.

Skipping Retrospectives — Making Your Scrum Work #17 – Age-of-Product.com
Continue reading Skipping Retrospectives? — Making Your Scrum Work #17

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