zx

Tag: Scrum Anti-Patterns

  • 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 — Berlin Product People GmbH

    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?”

    (more…)

  • 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 — Berlin Product People GmbH

    (more…)

  • 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 — Berlin Product People GmbH

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

    (more…)

  • 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 Will Cost You Dearly — Making Your Scrum Work #11 — Berlin Product People GmbH

    (more…)

  • 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 — Berlin Product People GmbH

    (more…)

  • 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

    (more…)

  • The ‘Developers Code’ Fallacy — Making Your Scrum Work #9

    TL; DR: The Developers Code Fallacy — They Should Talk to Customers, Too, Though

    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. The Developers Code Fallacy starts with the idea that Developers are rare and expensive and should focus on creating code. Business analysts or customer care agents can talk to customers instead. However, in practice, it has a diminishing effect on a Scrum team’s productivity and creativity. It is a sign for an organization still profoundly stuck in industrial paradigm thinking.

    Join me and explore the reasons and the consequences of this Scrum anti-pattern in 110 seconds.

    The Developers Code Fallacy — Making Your Scrum Work #9 — Berlin Product People GmbH

    (more…)

  • Three Wide-Spread Stakeholder Failures in 6:05 Minutes—Making Your Scrum Work #8

    TL; DR: Three Wide-Spread Stakeholder Failures

    There are plenty of Scrum stakeholder failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone. While the Scrum Guide makes numerous references to stakeholders in Scrum, stakeholders themselves are no official role (accountability), no matter their crucial contribution to a Scrum team’s overall success.

    Explore with me three widespread examples of how stakeholders fail their Scrum teams in three short video clips, totaling 6 minutes and 5 seconds.

    Three Wide-Spread Stakeholder Failures in 6:05 Minutes—Making Your Scrum Work #8 — Berlin Product People GmbH

    (more…)

  • Gold-Plating Beyond Done — Making Your Scrum Work #7

    TL; DR: Gold-Plating Beyond Done

    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. However, creating Product Increments that “over-deliver” in scope or quality — also known as gold-plating — with regard to the previous refinement agreement demonstrates that the Developers need to acquire a more entrepreneurial mindset and embrace their responsibility.

    Join me and explore the reasons and the consequences of this Sprint anti-pattern in 109 seconds.

    Gold-Plating Beyond Done — Making Your Scrum Work #7 — Berlin Product People GmbH

    (more…)

  • Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5

    TL; DR: Three Wide-Spread Product Owner Failures

    There are plenty of Product Owner failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.

    Explore with me three widespread examples of how Product Owners fail their team in three short video clips, totaling 6 minutes and 9 seconds.

    Three Wide-Spread Product Owner Failures in 6:09 Minutes—Making Your Scrum Work #5 — Berlin Product People GmbH

    (more…)