Are we still on track to accomplish the Product Goal? Moreover, how did the previous Sprint contribute to our Scrum team’s mission? Answering these questions and adapting the Product Backlog in a collaborative effort of the Scrum Team with internal and external stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns.
What event could better embody Scrum’s principle of empiricism than the Sprint Retrospective? I assume all peers agree that even the simplest form of a Retrospective—if only held regularly—is far more helpful than having a fancy one once in a while, not to mention having none. Moreover, I am convinced there is always room for improvement; just avoid dogmatism. Hence, learn more about 21 common Sprint Retrospective anti-patterns that will hold back your Scrum team.
The Sprint Planning is a core event that defines how your customers’ lives will improve with the following Product Increment. Learn more on how to improve its effectiveness by avoiding 20 common Sprint Planning anti-patterns.
Scrum is a tactical framework to build products, provided you identify what is worth making in advance. But even after a successful product discovery phase, you may struggle to create the right thing in the right way if your Product Backlog is not up to the job—garbage in, garbage out. The following article points to 27 common Product Backlog anti-patterns – including the Product Backlog refinement process – limiting your Scrum team’s success.
Welcome to the Sprint anti-patterns article from my series on Scrum anti-patterns, covering the three Scrum roles—pardon me: accountabilities—and addressing the contributions of stakeholders and the IT/line management. Moreover, I add 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 my experience, the Daily Scrum is the Scrum event with the highest anti-pattern density among all events. Learn more about Daily Scrum anti-patterns that threaten your Scrum team’s success, from becoming a reporting session to assignments to answering these three questions.
