liveBook · Manning

Capability mapping

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Capability Mapping is a technique for identifying and organizing the business capabilities an organization provides.

Capability mapping identifies and organizes the capabilities an organization provides. It supports conversations about domains, service boundaries, team structures, and architecture modernization rather than producing a definitive artifact. section 15.2

Use capability mapping to:

  • Map an organization and identify candidate domains and service boundaries. section 15.2
  • Connect business boundaries with team and software boundaries. section 15.2
  • Facilitate valuable conversations through iterative visual models. section 15.2

Broadband self-fulfillment

A telco mapped the capability of customer self-fulfillment for an internet broadband package. Its operational value stream included placing the order, preparing and shipping equipment, delivering it, and self-installing and activating broadband. These steps became initial candidates for team and software boundaries. section 15.2

Figure 15.2 Partial view of the customer self-fulfillment of an internet broadband package operational value stream

Explore the partial operational value stream used to examine the customer self-fulfillment capability. section 15.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Maps capabilities and value-stream steps, then validates proposed boundaries against team relationships and dependencies.
Examples
Uses broadband self-fulfillment, from ordering through activation, as an operational value-stream example.
What it assumes
Builds on interviews and diverse perspectives about the organization and its operational value streams.
What you can do after
Apply it via collaborative mapping to identify candidate domains, boundaries, and options for team evolution.
How it connects
Connects EventStorming, Value Stream Mapping, domains, service boundaries, and Team Topologies.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.