Key takeaways
- A business capability describes what the enterprise can accomplish.
- EA capability enables architecture work to be performed and governed.
- Capability Architecture and Architecture Capability are not interchangeable terms.
A capability describes an ability
A capability is an ability to achieve an outcome. A business capability, such as processing a refund, may use people, processes, information, and tools. It remains recognizable even when a process or application changes. Describing capabilities supports discussion of investment and performance without immediately restricting the discussion to a solution.
A Capability Architecture addresses architecture at the scale of a capability or a limited set of capabilities. It may specify necessary changes and increments. This description level should not be confused with Architecture Capability, which concerns the organization’s ability to perform architecture work.
Operating the EA practice
An Enterprise Architecture Capability depends on suitable organization, roles, skills, processes, tools, and governance. It must operate as a real activity: managing resources, finances, performance, risks and opportunities, quality, communication, suppliers, configuration, environment, and services provided. Creating a repository or appointing an architect alone does not establish an effective practice.
- Define expected outcomes from the architecture practice.
- Identify responsibilities and the resources required.
- Measure the service provided and improve capability over time.
TERMS TO KNOW
The terms, in context.
- Business Capability
- Ability of an enterprise to achieve a business outcome.
- Architecture Capability
- Organization and resources enabling architecture practice.