This post originated from an RSS feed registered with Agile Buzz
by Franco Martinig.
Original Post: Agile Requirements: a Definition of Ready Checklist
Feed Title: Scrum Expert
Feed URL: http://feeds.feedburner.com/ScrumExpert
Feed Description: Resources, News and Tools for the ScrumMasters, Product Owners and Agile Developers
We all know the “Definition of Done” used in Scrum for items that should be potentially shippable to the customer at the end of the sprint. In his book Essential Scrum, Kenneth Rubin discusses the “Definition of Ready” that applies to product backlog items that should be ready to be developed before the start of the sprint. Grooming the product backlog should ensure that items at the top of the backlog are ready to be moved into a sprint so that the development team can confidently commit and complete them by the end of a sprint. Some Scrum teams formalize this idea by establishing a definition of ready. You can think of the definition of ready and the definition of done as two states of product backlog items during a sprint cycle. Both the definition of done and the definition of ready are checklists of the work that must be completed before a product backlog item can be considered to be in the respective state. An example of a definition-of-ready checklist for product backlog items is given below. Definition of Ready * Business value is clearly articulated. * Details are sufficiently understood by the development team so it can make an informed decision as to whether it can complete the product backlog item (PBI). * Dependencies are identified and no external dependencies would block the PBI from being completed. * Team is staffed appropriately to complete the PBI. * The PBI is estimated and small enough to comfortably be completed [...]