The Meta-Retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action items. It comprises team members of one or several product teams—or a representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers. Meta-Retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product.
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.
Can we or should we change Scrum, or is it a sacrilege to tweak the ‘immutable’ framework to accommodate our teams’ and organizations’ needs?
Not so fast; don’t just dismiss augmenting Scrum as leaving the path, contributing to the numerous Scrumbut mutations, giving Scrum a bad name. However, in our rapidly evolving business landscape, sticking rigidly to traditional Scrum by the book could be a straightjacket stifling innovation, user focus, and adaptability.
From ensuring cultural compatibility to facing technical debt challenges and emerging technologies, discover ten compelling reasons why augmenting Scrum isn’t just okay—it’s necessary for modern teams.
Read on to discover when and how to adapt Scrum responsibly without diluting its essence.
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.
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.
TL; DR: The Minimum Viable Library for Scrum Masters
The Minimum Viable Library is available! Explore a series of carefully curated collections of essential books, newsletters, podcasts, and tools to elevate your agile expertise.
Read on and learn how the recommendations for Scrum Masters cover a wide range of topics, including Scrum, servant leadership, customer value creation, coaching teams, improving team dynamics through Retrospectives, and navigating agile enterprise transformations.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
3rd Party Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!