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.
by Stefan Wolpers|Agile and ScrumAgile TransitionWorkshops
TL; DR: Introducing the “Anti-Patterns Canvas”
Join me in developing the Anti-Patterns Canvas, a dynamic and free tool that extends the insights of the “Scrum Anti-Patterns Guide” book. Share your expertise through the survey, see below, and test-drive tools, practices, and exercises through a series of upcoming Hands-on meetups. In other words, help me create a resource that enhances agile practice and value creation.
Learn how outdated organizational structures manifest themselves in system-level Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization. We cover the perils of a lack of transparency, limited to non-existing leadership support, and why penny-pinching is the wrong approach.
by Stefan Wolpers|Agile and ScrumAgile TransitionVideos
TL; DR: Tackling Fake Agility with Johanna Rothman
Your team is supposed to use an agile approach, such as Scrum. But you have a years-long backlog, your standups are individual status reports, and you’re still multitasking. You and your team members wish you had the chance to do great work, but this feels a lot like an “agile” death march. There’s a reason you feel that way. You’re using fake agility—a waterfall lifecycle masquerading as an agile approach. Worse, fake agility is the norm in our industry. Now, there is light at the end of the tunnel; let’s delve into Tackling Fake Agility with Johanna Rothman!
In this article, we uncover typical ways in which Scrum teams fail stakeholders, from overpromising results to poor risk communication to neglecting feedback. Moreover, we will also explore actionable strategies to overcome these anti-patterns by building trust, aligning priorities, and enhancing collaboration for successful product development.
TL; DR: Sprint Anti-Patterns Holding Your Teams Back
Welcome to Sprint anti-patterns! This article covers the three Scrum accountabilities (formerly roles) and addresses interferences of stakeholders and IT/line management with this crucial Scrum event. Moreover, I added some food for thought. For example, could a month-long Sprint be too short for accomplishing something meaningful? And if so, what are the consequences?
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!
