Simplify Your Work by Slicing
When slicing a backlog item, we're taking a complex problem and paring it down into smaller problems, which are easier to solve and build.
Get the Problem Right or You'll Get the Solution Wrong
Good software solves the customer's problems, but to provide the right solution, you must start with the right problem.
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!
The Hidden Cost of Big Backlog Items
In creative work like software development, bigger always means riskier. Large backlog items increase complexity, delay feedback, and compromise quality. This post breaks down why “smaller is smarter” in Scrum and how decomposing large Product Backlog Items (PBIs) can dramatically improve your team’s flow, confidence, and results.
Backlog Refinement Part 6: Slicing Backlog Items con't
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!
Backlog Refinement Part 5: Slicing Backlog Items
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!
Backlog Refinement Part 4: Estimating Backlog Items
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!
Backlog Refinement Part 2: How Small is Small Enough?
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!