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?
In this fascinating talk, Michael introduced the concept of dysfunction mapping, a tool developed over years of trial and error aimed at creating a repeatable way to find, theme, and ultimately solve organizational dysfunction.
📺 Watch the video now: Dysfunction Mapping — Michael Lloyd at the 58. Hands-on Agile Meetup.
Are you ready to transform your Scrum practices and elevate your agile journey? Dive into my exclusive, free email course based on the acclaimed “Scrum Anti-Patterns Guide” book. This course is a treasure trove of insights, offering a sneak peek into the crucial anti-patterns that could hinder your team’s success.
This course illuminates the common pitfalls in Scrum roles — from the Scrum Master to the Product Owner and stakeholders — and Scrum events. You’ll gain an understanding of the subtle missteps, team dynamics, and resulting patterns.
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!
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.
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.
