Concise Scope
Agile scrum utilizes a product backlog as the primary definition of scope. The product backlog is best defined as the communications tool where the product owner takes the vision of the product and translates it into high level requirements. Those requirements are labeled features. A feature is a desired element or component of functionality that the product owner believes is required to deliver a product.
Features are listed, prioritized and adjusted for release planning based on risks, dependencies, and business value. Management of the product backlog using quality standards for prioritization and risk evaluation will produce greater business value.
A well-managed backlog contains four characteristics classified through the acronym DEEP that Mike Cohn and Rich Pichler accurately categorized. DEEP stands for:
- D –Detailed appropriately. Features should be descriptive enough so that smaller user stories can be created for delivery by the scrum team.
- E –Emergent. The product backlog is a living document and any Agile team will respect the fact that change is encouraged. Not just for the sake of change but, for the benefit of changes needed to embrace fluidity in the market.
- E –Estimated. A high level estimate should be attempted by the scrum team so that release planning can take place.
- P –Prioritized. Prioritization is not a fixed effort. This is another component of delivering business value by embracing change.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: