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.
Many Scrum events seem simple, but aren't. The Daily Scrum seems to be the event that causes the most problems for teams.
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.
Teams that "Swarm" backlog items find it's a better way to get work done than approaches that lead to handoffs and continuity loss.
Many organizations transitioning to Agile Development suffer from a preconceived idea that coding tasks and testing tasks should be seen as separate activities.
This blog post seeks to provide some tips you can use to help your teams successfully do large item estimation. Part 6 of my series on Backlog Refinement!
This blog post seeks to provide some tips you can use to help your teams successfully do large item estimation. Part 5 of my series on Backlog Refinement!
Keeping the Product Backlog estimated is hard because of constant changes. What's the best estimation technique? Part 4 of my series on Backlog Refinement!
How do you make sure the Scrum team refines enough backlog items for the next Sprint? Part 3 of my series on Backlog Refinement!
How do you know how small to make your backlog items before you stop refining them and move on to something else? Part 2 of my series on Backlog Refinement!
While coaching Scrum teams I've noticed how difficult effective backlog refinement is, so I wrote a blog post series on how backlog refinement works.
Estimation isn't about knowing how long something will take to build but about determining how complicated something is, then using practical experience.