A regular rhythm of working.

In Benefits Realisation Management (BRM) context – a capability is ‘the set of outputs required to create an outcome’.
Note – ‘capability’ is often used interchangeability with the term ‘business capability’, which is not entirely true or correct. Business Capabilities consists of ‘people, process and technology’. Often ‘Technology’ stakeholders refer to the collective ‘technology’ they build, develop and/or maintain as ‘capabilities’. To be explicitly clear and to avoid confusion, and therefore the 70% failure rate in transformations, ‘a capability’ in that context strictly refers to or relates to ‘technology only’. Also see Business Capability.

Situation where quick and dirty design choice is made to meet a deadline or milestone, which end up costing unnecessary time and effort to undo or correct when time and/or money comes available.

In terms of enterprise architecture and design, a concern is a worry or area of worry a stakeholder has that results in a tension on the project, program or transformation. There is a cause-and-effect relationship before concern -> tension, which is addressed by (design) principles. Concerns are often related to scope (whats in, and whats out), which cause a tension, which is addressed by design principle(s).

A Customers needs (or requirement) expected from a given product or service that addresses their stated (or unstated) concern(s).

The quantitative measure of a Customer (internal or external) need. See Critical to Customer (CTC) above.

In terms of assumptions – an indicator of the level of how disruptive the change will be to the Programme.

Acronym for Create, Read, Update and Delete. Used to describe (shorthand) the basic function or User requirements.