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. For example, what if there is no Sprint Goal — Sprint after Sprint? What if the Scrum team is always only working on a random assortment of work items that seem to be the most pressing at the moment of the Sprint Planning?
Join me and delve into the importance of the Sprint Goal for meaningful work as a Scrum team in less than two minutes.
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. For example, what if your Scrum team repeatedly faces unengaged stakeholders at the Sprint Review? How can the Scrum team stay on track in accomplishing the Product Goal when a vital feedback loop is missing?
Join me and delve into how to support your stakeholders in living up to their part of the collaboration with the Scrum team in less than two minutes.
Trust is the beginning of everything. I am hesitant to recycle an old slogan of a banking institute. However, in the context of becoming a learning organization and embracing business agility, it condenses the main challenge perfectly: How shall we convince the incumbents with vested interests in the status quo to give the new way of working the benefit of the doubt? Join me and delve into how distrust manifests and what we can do to earn stakeholder trust.
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. What if, for example, not all of your Scrum team’s members feel enthusiastic about the Sprint Retrospective, the critical event when the Scrum team inspects itself? How can you help them become dedicated supporters instead? Join me and delve into how to avoid teammates feeling like prisoners of Retrospectives in less than two minutes.
After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses Scrum Developer anti-patterns, covering all Scrum Events and the Product Backlog artifact. Continue reading and learn more about what to look out for if you want to support your teammates who build the Increment.
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization.
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!
