endUser stories and Bugs should meet the Definition of Ready before they can be pulled into a sprint for delivery.
| Table of Contents | ||
|---|---|---|
|
...
Do we have a shared understanding of the story?
We can describe the technical approach for how we're going to build the solution. Developer
We can describe how we haven't broken anything else by building functionality for this story. Developer
We know how we can demonstrate that the story meets its acceptance criteria. Developer
The story can be estimated, developed, tested and deployed independently of other functionality. Lead Dev
Incoming dependencies have been identified and resolved (either cleared or fulfilled). Lead Dev
The Story is linked to (requires) other tasks or stories that it is technically dependent on. Lead Dev
There is enough information to reasonably estimate the delivery effort. Lead Dev
Story Points have been captured. Scrum Master
Key development tasks are outlined. Lead Dev
There is enough information to develop a test plan. Test Lead
The story has been sized appropriately. Developer
The story is small enough to start and finish in a single iteration; ideally 1-2 days, and really less than half the sprint length. Lead Dev
When a story meets the above criteria it is ready for acceptance into the Sprint Backlog
...