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.
👉 Join the Anti-Patterns Canvas survey here.
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.
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.
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.
The feature factory fate is not inevitable; there is hope to avoid becoming a mere cog in the machinery. Learn how!
In many large organizations, Scrum teams fall into the ‘feature factory’ trap, focusing more on churning out features than creating real value. It’s too bad that this shift undermines Agile principles and hampers long-term success and innovation. Let’s discuss how and why this happens and what we can do to break the chains of the feature factory.
