After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. Learn more about what to look out for if you want to support your fellow teammates.
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns which easily can impede any agile transition.
Welcome to the Sprint anti-patterns article from our series on Scrum anti-patterns, covering not just the three Scrum roles, but also the stakeholders as well as the IT management.
If you are working as a Product Owner, there is—very likely—room for improvement. This list of some of the most common Product Owner anti-patterns might be a starting point. Hence, if you recognize some anti-patterns in your daily work, why don’t you ask the rest of the Scrum Team for support? The Product Owner anti-patterns list is a good starting point for a retrospective.
Sprint Planning is a core event, defining how your customers’ lives will improve with the next Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns.
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 post on Scrum anti-patterns how you can identify if your Scrum Master needs support from the team.
