zx

Tag: Scrum Anti-Patterns

  • New in 2024: Assessments, Practices, Exercises, and Tools to Help You Excel

    TL; DR: Tools to Help You Excel in 2024

    Having just completed the Scrum Anti-Patterns Guide book, I will turn my focus to 2024 with new projects that build on the foundation laid by the book. I plan to dedicate the upcoming year to empowering agile practitioners through various new tools, workshops, and community events. The tools to help you excel will enhance your skill sets and equip you to thrive amidst professional challenges.

    Join your peers for a journey of interactive learning and community engagement in 2024!

    Tools to Help You Excel in 2024: Assessments, Practices, Exercises — Berlin-Product-People.com

    (more…)

  • How To Spot Successful Scrum Masters

    TL; DR: How To Spot Successful Scrum Masters

    In this article, I unravel the secrets of what makes a Scrum Master not just good but amazingly outstanding. From regularly achieving Sprint Goals, delivering value to customers, and building stakeholder rapport easily, discover the traits that set apart successful Scrum Masters.

    Moreover, we also shed light on the pitfalls to avoid if you want to keep the respect of your teammates and probably your job.

    Successful Scrum Masters — Berlin-Product-People.com

    (more…)

  • The Scrum Trap: How Unfit Practices Will Harm Return on Investment

    TL, DR: The Scrum Trap

    Scrum is a purposefully incomplete framework. Consequently, it needs to be augmented with tools and practices to apply its theoretical foundation to an organization’s business reality: what problems shall be solved for whom in which market? Moreover, there is an organization’s culture to take into account. However, the intentional “gap” is not a free-for-all to accept whatever comes to mind or is convenient. Some tools and practices have proven highly effective in supporting Scrum’s application and reaping its benefits. And then there are others — the Scrum trap.

    Let’s look at what practices and tools for collaboration and team building are not helpful when used with Scrum.

    The Scrum Trap: How Unfit Practices Will Harm Return on Investment — Berlin-Product-People.com

    (more…)

  • Escaping the Feature Factory — Refocussing From Output to Outcome

    TL; DR: Escaping the Feature Factory

    The feature factory fate is not inevitable; there is hope to avoid becoming a mere cog in the machinery. Learn how!

    In many large organizations, Scrum teams fall into the ‘feature factory’ trap, focusing more on churning out features than creating real value. It’s too bad that this shift undermines Agile principles and hampers long-term success and innovation. Let’s discuss how and why this happens and what we can do to break the chains of the feature factory.

    Escaping the Feature Factory: From Output-focused Workers to Value-driven Innovators — Berlin-Product-People.com.

    (more…)

  • Scrum Team Failure — Scrum Anti-Patterns Taxonomy (3)

    TL; DR: Scrum Team Failure

    This post on Scrum team failure addresses three categories from the Scrum anti-patterns taxonomy that are closely aligned: Planning and process breakdown, conflict avoidance and miscommunication, and inattention to quality and commitment, often resulting in a Scrum team performing significantly below its potential.

    Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.

    This is the third of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The other two articles, see below, address adhering to legacy systems, processes, practices, and communication and collaboration issues.

    Scrum Team Failure — Scrum Anti-Patterns Taxonomy (3) — Berlin-Product-People.com

    (more…)

  • Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2)

    TL; DR: Lost in Communication and Collaboration

    Lost in Communication and Collaboration addresses two categories from the Scrum anti-patterns taxonomy that are closely aligned: ineffective collaboration at the stakeholder level, often resulting in an unsuited reporting system based on misaligned metrics.

    Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.

    This is the second of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The third article will address failures and breakdowns in planning, process, collaboration, and alignment within the Scrum framework.

    Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2) — Berlin-Product-People.com

    (more…)

  • The Peril of Adhering to Legacy Systems, Processes, and Practices — Scrum Anti-Patterns Taxonomy (1)

    TL; DR: Adherence to Legacy Systems, Processes, and Practices

    Administrative overreach and micromanagement in Scrum mainly arise from clinging to legacy systems and traditional (management) practices, leading to rigidity and misapplication of Agile principles. The excessive control by stakeholders and the management level stifles creativity and adaptability, disrupting planning and hindering a Scrum team’s growth. Moreover, these categories from the Scrum anti-patterns taxonomy often emphasize an unbalanced focus on short-term gains, neglecting long-term strategy, value creation, and the essential alignment among all stakeholders to succeed in uncertainty.

    Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the long-term sustainability of the organization.

    This is the first of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The following article will address communication and collaboration issues at the team and organizational levels.

    Adherence to Legacy Systems, Processes, and Practices — Scrum Anti-Patterns Taxonomy (1) — Berlin-Product-People.com

    (more…)

  • The Expensive Folly of the Oversized Product Backlog

    TL; DR: The Costs of an Oversized Product Backlog

    Some Product Owners believe that a comprehensive Product Backlog is the best way to accomplish the Product Goal and be fully transparent simultaneously—never let a possibly valuable idea slip away. However, a comprehensive backlog may quickly become an oversized Product Backlog with unintended side effects.

    Learn more about an oversized Product Backlog’s negative impact on innovation, your Scrum team’s ability to create value, and your relationship with stakeholders.

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

    (more…)

  • Jira Anti-Patterns and How to Overcome Them

    TL; DR: Jira Anti-Patterns

    If you ask people to come up with popular attributes for “Agile” or “agility,” Scrum and Jira will likely be among the top ten featured. Moreover, in any discussion about the topic, someone will mention that using Scrum running on top of Jira does not make an organization agile. However, more importantly, this notion is often only a tiny step from identifying Jira as a potential impediment to outright vilifying it. So in March 2023, I embarked on a non-representative research exercise to learn how organizations misuse Jira from a team perspective as I wanted to understand Jira anti-patterns.

    Read on and learn more about how a project management tool that is reasonably usable when you use it out of the box without any modifications turns into a bureaucratic nightmare, what the reasons for this might be, and what we can do about it.

    Jira Anti-Patterns — Berlin-Product-People.com

    (more…)

  • The Three Daily Scrum Questions Won’t Die — Making Your Scrum Work (29)

    TL; DR: The Three Daily Scrum Questions Won’t Die

    The Daily Scrum serves a single purpose: inspecting the progress toward the Sprint Goal by reflecting on yesterday’s learning. Then, if the need should arise, the Developers adapt their plan to accomplish the Sprint Goal. While the theory may be generally accepted, applying the idea to the practice is more challenging. One of the recurring issues is the continued popularity of the “three Daily Scrum questions” from the Scrum Guide 2017.

    Let’s reflect on why answering these obsolete Daily Scrum questions negatively influences the Scrum team.

    The Three Daily Scrum Questions Won’t Die — Making Your Scrum Work (29) — Berlin-Product-People.com

    (more…)