zx

Tag: Scrum Anti-Patterns

  • 21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams

    21 Sprint Retrospective Anti-Patterns Impeding Scrum Teams

    TL; DR: Sprint Retrospective Anti-Patterns

    What event could better embody Scrum’s principle of empiricism than the Sprint Retrospective? I assume all peers agree that even the simplest form of a Retrospective—if only held regularly—is far more helpful than having a fancy one once in a while, not to mention having none. Moreover, I am convinced there is always room for improvement; just avoid dogmatism. Hence, learn more about 21 common Sprint Retrospective anti-patterns that will hold back your Scrum team.

    Sprint Retrospective Anti-Patterns — Scrum Anti-Patterns Guide — Berlin Product People GmbH

    (more…)

  • 20 Sprint Planning Anti-Patterns

    20 Sprint Planning Anti-Patterns

    TL; DR: Sprint Planning Anti-Patterns

    The Sprint Planning is a core event that defines how your customers’ lives will improve with the following Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns.

    20 Sprint Planning Anti-Patterns — Berlin Product People GmbH

    (more…)

  • Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help

    Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help

    TL; DR: Scrum Master Anti-Patterns

    The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself.

    Read on and learn in this post on Scrum anti-patterns how you can identify if your Scrum Master needs support from the team.

    Scrum Master Anti-Patterns — 20 Signs Your Scrum Master Needs Help — Berlin Product People GmbH

    (more…)

  • 27 Product Backlog Anti-Patterns

    27 Product Backlog Anti-Patterns

    TL; DR: 27 Product Backlog and Refinement Anti-Patterns

    Scrum is a tactical framework to build products, provided you identify what is worth making in advance. But even after a successful product discovery phase, you may struggle to create the right thing in the right way if your Product Backlog is not up to the job—garbage in, garbage out. The following article points to 27 common Product Backlog anti-patterns – including the Product Backlog refinement process – limiting your Scrum team’s success.

    27 Product Backlog and Refinement Anti-Patterns — Berlin Product People GmbH

    (more…)

  • Daily Scrum Anti-Patterns: 24+2 Ways to Improve as a Scrum Team

    Daily Scrum Anti-Patterns: 24+2 Ways to Improve as a Scrum Team

    TL; DR: 24+2 Daily Scrum Anti-Patterns

    In my experience, the Daily Scrum is the Scrum event with the highest anti-pattern density among all events. Learn more about Daily Scrum anti-patterns that threaten your Scrum team’s success, from becoming a reporting session to assignments to answering these three questions.

    Daily Scrum Anti-Patterns: 24+2 Ways to Improve as a Scrum Team — Berlin Product People GmbH

    (more…)

  • How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches

    TL; DR: How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches to Avoid

    One of my favorite exercises from my Professional Scrum Product Owner classes is how to best sabotage a Product Owner as a member of the middle management. The exercise rules are simple: You’re not allowed to use any form of illegal activity. So, outsourcing the task to a bunch of outlaws is out of the question. Instead, you are only allowed to use practices that are culturally acceptable within your organization.

    Read on and learn more on how to best sabotage a Product Owner from the exercise results of more than twenty PSPO classes. (I edited the suggestions for better readability.)

    How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches — Berlin Product People GmbH

    (more…)

  • How to Sabotage A Scrum Master — 44 Anti-Patterns from the Trenches

    TL; DR: How to Sabotage A Scrum Master — 44 Anti-Patterns from the Trenches to Avoid

    One of my favorite exercises from my Professional Scrum Master classes is how to best sabotage a Scrum Master as a member of the middle management. The exercise rules are simple: You’re not allowed to use any form of illegal activity. So, outsourcing the task to a bunch of outlaws is out of the question. Instead, you are only allowed to use practices that are culturally acceptable within your organization.

    Read on and learn more on how to best sabotage a Scrum Master from the exercise results of more than twenty PSM I and PSM II classes. (I slightly edited the suggestions for better readability.)

    How to Sabotage A Scrum Master — 44 Anti-Patterns from the Trenches — Berlin Product People GmbH

    (more…)

  • What Capacity Check? — Making Your Scrum Work #23

    TL; DR: Ignoring the Capacity Check during Sprint Planning

    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, the Developers are ignoring a capacity check during the Sprint Planning, and as a result, the Scrum team creates a Sprint Goal that most likely cannot be accomplished.

    Join me and delve into the effects of this trust-shattering practice in less than 80 seconds.

    What Capacity Check? — Making Your Scrum Work #23 — Berlin Product People GmbH

    (more…)

  • Maximizing Utilization, Ignoring Slack Time — Making Your Scrum Work #22

    TL; DR: Maximizing Utilization as a Relic from the Industrial Management Past

    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, what if the focus of the organization is on the maximizing utilization of the “workers” of the Scrum teams? What if the organization is still stuck deeply in industrial paradigm thinking, ignoring the benefits of slack time for the creation of value in the field of knowledge work?

    Join me and delve into the effects of this outdated management principle in 60 seconds.

    Maximizing Utilization, Ignoring Slack Time — Making Your Scrum Work #22 — Berlin Product People GmbH

    (more…)

  • Overruling the Product Owner? — Making Your Scrum Work #21

    TL; DR: Overruling the Product Owner

    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, what if the stakeholders—who bring the budget that is funding your Scrum team—insist on calling the shots by overruling the Product Owner’s prerogative to define the composition and the ordering the Product Backlog? What if your stakeholders suffer from the “my budget, my feature” syndrome?

    Join me and delve into the effects of overruling the Product Owner in less than 140 seconds.

    Overruling the Product Owner? — Making Your Scrum Work #21 — Berlin Product People GmbH

    (more…)