Maturity mapping represents capabilities as practices that develop through context-specific stages: Novel, Emerging, Good, and Best. Unlike a generic skills matrix or maturity model, it relates each practice to the problem a team is solving and the business context around it. section 12.2.3
Use maturity mapping collaboratively:
- State the business problem and the team’s objective. section 12.2.3
- Create a value chain connecting the business problem to the capabilities and practices needed to address it. section 12.2.3
- Place each practice at Novel, Emerging, Good, or Best maturity in relation to that context. section 12.2.3
- Use the resulting map to discuss capability development and how teams should evolve as business needs change. section 12.2.3 section 12.7
Modernizing architecture
A team moving toward microservices may need new practices for cross-cutting concerns and observability. Mapping those practices against the team’s modernization problem reveals which capabilities require development instead of applying a generic maturity rating. section 12.2.3
