Explore with me three widespread examples of how stakeholders fail their Scrum teams in three short video clips, totaling 6 minutes and 5 seconds.
Join the DZone community and get the full member experience. 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. Let’s refresh our memories regarding stakeholders according to the 2020 Scrum Guide. While stakeholders are not an official accountability, the Scrum Guide makes numerous references to stakeholders in Scrum: Source: The Scrum Guide on stakeholders. (This aggregation is from the Scrum Guide 2020 Reordered.) Let me point at three Scrum stakeholder failures that have the potential to derail your organization’s attempt at achieving business agility with Scrum: In my experience, the Sprint Review acceptance gate by stakeholders is an anti-pattern typical for organizations that are still rooted in the industrial paradigm, exercising command & control. Some of the reasons for this anti-pattern are: Generally, this example among stakeholder failures is a sign for an agile transformation that is not fully supported by all stakeholders.
