TL;DR: Use Burn-Down Charts to Discover Scrum Anti-Patterns
A burn-down chart tracks the progress of a team toward a goal by visualizing the remaining work in comparison to the available time. So far, so good. More interesting than reporting a status, however, is the fact that burn-down charts also visualize scrum anti-patterns of a team or its organization.
Learn more about discovering these anti-patterns that can range from systemic issues like queues outside a team’s sphere of influence and other organizational debt to a team’s fluency in agile practices.
TL; DR: Lipstick Agile — Happiness in the Trenches?
Have you noticed how many people in the agile field are unhappy with their work situation — caught in a lipstick agile situation where an organization already struggles doing agile? (Not to mention ‘becoming agile.’)
Scrum masters, and agile coaches who are close to either burnout or indifference. Product owners who “own” the product by name only, and developers who are questioning why Scrum a) skips all the practices that make XP work, and b) often turns out to be just another form of micromanagement.
Scrum Master Anti-Patterns: The reasons why scrum masters violate the spirit of the Scrum Guide are multi-faceted. They run from ill-suited personal traits and the pursuit of individual agendas to frustration with the team itself.
Read on and learn in this final post on scrum anti-patterns how you can identify if your scrum master needs support from the team to up his or her agile game.
After rebuilding an existing application on a new tech stack within time and under budget our team had an overall retrospective with stakeholders this week to identify systemic issues. We found more than 20 problems in total and derived eight detailed recommendation the organization will need to address when moving forward to the next level of agile product creation.
Read on and learn how we achieved this result in under two hours with an overall retrospective attended by 16 people.
Scrum has proven to be an effective product delivery framework for digital products like applications or apps. However, Scrum is equally suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The product owner miraculously identifies what is the best way to proceed as a team by gating and prioritizing the product backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for himself, product discovery anti-patterns emerge.
From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.