DONEness Definitions (DoD)
What's the one thing YOU could do as a Scrum Master to improve your team's reliability, quality, and productivity? Read on and find out!
Don’t Manage Your Product, Own It!
If your Scrum teams aren't seeing the quality, value, and productivity improvements you were hoping for, it's possible that they don't understand their roles.
Keep Your Sprints Short
Scrum teams are responsible for choosing sprint length and are encouraged to experiment with different sprint lengths, but shorter sprints are easier to manage.
Keep Your Eyes on the Sprint Goal
In this article, we'll discuss how a team bares responsibility for the Sprint and what should be done if they can’t get everything done they committed to.
Plan Only Small Backlog Items
Bigger requirements are more complex, which typically have greater risk, which leads to more cost and/or waste. In other words, bigger is DEFINITELY not better!
Avoid Adding Content to a Sprint
One of the worst things we can do to our teams is allow too many changes to the content of the Sprint after the Sprint has been planned.
Never Extend a Sprint
Scrum Sprints provide empiricism, part of the Agile core beliefs, which is why extending a Sprint is never a good idea!
Keep Your Daily Scrum Short
Many Scrum events seem simple, but aren't. The Daily Scrum seems to be the event that causes the most problems for teams.
Keep Your Work In Process Low
The fastest team productivity killer is working on 3+ backlog items at once. You'll end up with a team that's great at starting work, but lousy at finishing it.
Swarming Backlog Items
Teams that "Swarm" backlog items find it's a better way to get work done than approaches that lead to handoffs and continuity loss.
Teaching the Scrum Framework
It's critical everyone on a new Scrum Team starts with the same understanding of Scrum. A learning structure called “ShuHaRi” can be related to teaching Scrum.
I Think We Broke Something… Somewhere
Many organizations transitioning to Agile Development suffer from a preconceived idea that coding tasks and testing tasks should be seen as separate activities.