Introduction
...
Alternatively one could choose to define capability from the architectural unification approach POLDAT
- Process (business processes)
- Organisation (structures)
- Location (Geographical information)
- Data (models, life cycles, security etc)
- Application (software, security, interoperability etc)
- Technology (infrastructure)
...
That's a very good question and it depends on your perspective; there are two several that I would like to describe and I am sure that you can think of others.
Partnership to deliver a goal(s)
...
Your defined capabilities are there to deliver a long term strategy. In the interim, pressure points force you to respond to them through short term goals. These short term goals require certain adjustments to your long term defined capabilities, the capability increments (up or down) result in work being down in your organisation to handle the pressure point. The aim is to not change the long term strategy (capabilities) but adjust them to deliver the short and long term goals.
Defining a capability
Defining a capability is an extensive task but once done can lead to a major simplification in the overall understanding and modelling of a problem domainenterprise.
Start by asking the following questions
...