Keep an eye out for these Scrum anti-patterns that threaten the effectiveness of your team’s development
“Celebrate and embrace the retrospective as an improvement opportunity for the entire team” Click To Tweet
Retrospective meetings–also known as team improvement meetings–help the team to uncover what went well and what could be improved from the last sprint or iteration. However, retros can become ineffective for a number of reasons:
I’ve seen too many poorly-organised backlogs in my time and they always result in a dysfunctional team. Badly organised backlogs come in a number of forms:
All of these create hazardous backlogs that waste time and energy. Pay attention to the backlog and ensure it’s well-organised before the start of every iteration. There have to be enough ‘ready’ product backlog items come out of Product Backlog Refinement for the next Sprint before of Sprint Planning.
Most companies rely on metrics and key performance indicators (KPIs) in some shape or form. However when those measurements are wrong they become useless. Make sure you have meaningful metrics so your team creates maximum impact in their delivery. You’ll want to know the following:
By having metrics in place to measure this you can make a noticeable difference to your team’s effectiveness and their development through each iteration.
I hope the video and tips above help you to identify and eliminate the dangerous Scrum anti-patterns that can emerge throughout a team’s journey together. It’s worth noting that there’s no such thing as perfect. But if you can keep an eye out for these warning signs you’ll stand a better chance of maintaining a highly-effective scrum team.
If you have any questions or topics you’d like me to cover, leave a comment below or send me a message through my website. Thanks for reading. See you next time!
Please log in again. The login page will open in a new window. After logging in you can close it and return to this page.