Ready to build

…scrum, about to pull in product backlog items into the sprint.

✣  ✣  ✣

{{{wish full}}}

• Downstream definition of ready equals the upstream definition of done.
• definition of ready means that any item can be pulled into the sprint.
• High quality definition of ready leads to high-quality work and speeds up velocity.

See below for a detailed example of a definition of ready.

Forces:

• Additional detail allow multiple teams to coordinate their work better.
• Additional detail can lead to more discussion.
• Too much detail limits creativity for implementers.
• Too little detail creates confusion and wastes time during implementation.
• The right level of detail in requirements, both functional and qualitative increases the immediately actionability of it.
• The useful power of the well-written specification increases with the frequencey ofreferring to it, and the number of people that need to interpret it.
• If there are questions about a specification, then the answer needs to be written down in the specification for reference by all future users of the specification, creating a living document of the collective memory of the system. The answers are not just 'discussed' oraly, and forgotten in practice.

Spend about 10% of the sprint time on grooming the items into ready to build state. Spend this time during the sprint, not during the planning session. Make it you goal to reduce the sprint planning meeting to a mere reconfirmation of the product backlog that emerged during the sprint's grooming sessions.

Only allow ready to build items into the sprint backlog, or risk to be bitten by debate, technical debt, cutting corners, and high pressure during the sprint.

Aim for quality in, quality out.

Therefore:

{{{therefore full}}}

✣  ✣  ✣

✣  ✣  ✣

Table below is based on Bill Wake's INVEST acronym. You can use it to structure your grooming sessions. It helps to uncover and discover otherwise unnoticed aspects and allows you to build quality in.

The second column is the test designed to proof the validity of the first.

Check	Proof
immediately actionable	The development teams have no no known questions regarding the what, why and for whom of the item and can immediately start implementing the item, working on it until it is done, completing it until it meets all criteria that allow it to be pulled into the next station. Therefore, a product backlog item must be detailed appropriately, e.g. as an enabling disclosure; and/or a page from the user manual, written by a mercenary analyst; To further improve actionability, consider providing: UI sketches, wireframes, and mock ups; scenarios; design ‘comics’ and story boards.
independent	Any dependancies are identified and the dependency count is less than three, meaning that the item is relatively independent and does not pull a lot of other items into the sprint.
understanding	The product backlog item details how it fulfills a need, goal or desire of the role or vibrant persona. The development team: says “Ah, we get it!”; explains the context, what, why (value creation) and for whom (vibrant persona) back to the product owner; and knows their implementation strategy, direction and conceptual design. A popular form for Template:Uss is: As a role I want to action so that benefit. Preferably, most stories obey this form. In some cases, you might consider using a vibrant persona for the the role. Typically, the ‘To’ part of a story, e.g. “To save a message” in a mail program, is the title of the story. The title of the story is something you can put into the user manual. Therefore, keep the title terse, concise, limited to a single short line. Make sure the title has both an action (verb) and object (noun) in it. Another way to test understandibility and intelligibility is to do the ambiguity test.
negotiable	The item is clear on the what, yet still leaves room for: how it will be implemented, meeting or exceeding the non-functional requirements and within the technological and architectural guidelines; and nudging details—functional, behavioral, technical, or otherwise that would benefit its use or implementation
valuable	The relative (business) value is clear and written on the item.
estimable	The item's relative implementation effort expressed in story points is written on the item by the development team, using techniques like planning poker.
sized appropriately	The item's estimated implementation effort is 8 story points or less.
testable	Crystal clear acceptance criteria for both the product owner and operations are associated with the item, probably written on the back of the item or documented in an automated test harness. Acceptance criteria help to: set scope; and define when an item is done and ready for demo and user acceptance test. Popular tools like Cucumber can be used to express these criteria and facilitate automated testing practices. Other useful practices include giving examples of: use case processes; reports; queries; input forms; and inspectors.
demonstrable	Either the development team or product owner or both can demonstrate the item when implemented. A good time for this is the sprint review meeting, but any other time during the sprint is also good. It gives a chance to immediately get some feedback and fold that in to current development. Defining and scripting the demonstration helps to: set scope; think through the many aspects of its use; find both happy and exceptional paths through the item's use; and validate earlier defined scenarios and their outcomes. A mercenary analyst can help verbalize the item in a concise, coherent and comprehensive way.

---