- 10.3 Overview of Features
- 10.4 Benefits of Feature Preparation
- 10.5 Feature Preparation Activities
- 10.6 Timing of Feature Preparation
- 10.7 Assessing Readiness
- 10.8 Accounting for Preparation Work: Tasks and Spikes
- 10.9 Specifying Features and Their Acceptance Criteria
- 12.4 MVP Planning
- 17.3 Why Do We Need a Scaled Agile Approach?
- 17.4 Planning: Choosing an Approach That Supports Inter-team Collaboration
- 17.8 Scaling the Agile Organization
- 18.6 Agile Corporate Culture
- 18.7 Overview of Principles and Practices for an Agile Corporate Culture
- 18.8 Three Principles for Applying Agile Practices
This chapter is from the book
This chapter is from the book
This chapter is from the book
10.7 Assessing Readiness
Use the checklist in Appendix A.7 to assess whether or not teams are ready for quarterly planning. Conditions in the checklist include that a vision, roadmap, and impacted users have been specified and that sufficient features (about ten to twenty) are ready.
10.7.1 Using the Feature Definition of Ready (Feature DoR)
Use the feature definition of ready (DoR) to determine if a feature is ready to be included in the quarterly plan or (in Kanban) to advance on to development.
The following are examples of the feature DoR conditions we saw in Chapter 6, “Preparing the Process.”
The feature is right-sized: The feature is small enough to be implemented within a quarter by one or more teams.
The feature has no (or minimal) dependencies on other features.
The feature is valuable.
All teams are committed.
The feature is estimable: The feature is understood well enough to be estimated.
For more on the feature DoR, see Chapter 6, section 6.5.7.6.