Our
Glossary
There are currently 18 names in this directory beginning with the letter B.
Backlog
List of requirements (i.e. User Stories, themes, epics), usually prioritised by business value. A Programme can have one or more backlogs. Business Architecture Programme, Work Stream, Spring, Test backlog with each subsequent backlog a subset of other Backlog i.e. Work stream backlog is a subset of the Programme backlog; Sprint backlog is a subset of the works tram backlog; Test Backlog is a subset of the Spring Backlog etc.
Benefit Type
Intermediate: a benefit that occurs early, that contributes to an End Benefit; End: achievement of a final benefit, that is dependent on the achievement of one or more Immediate Benefits.
Benefits (Business)
An outcome of an action or decision that contributes towards meeting one or more business (strategic) objectives. Benefits are the result of capabilities delivered and transitioned into and used by the Business Organisation, that produce positive outcomes for the business, that through their ongoing use, lead to the realization of benefits.
Benefits Owner
A person responsible for the realisation benefits. Can be an individual or group of stakeholders. According to the Managing Successful Programmes (MSP), this responsibility usually lies with the Senior Responsible Officer (SRO).
Benefits Profile
A comprehensive description of a single benefit, including all its attributes and dependencies.
Benefits Realisation Management (BRM)
The framework and process of Organisation and managing Benefits, so that planned benefits, arising from investment in change, are actually achieved.
Benefits Realisation Plan (BRP)
The artefact which shows how and when all benefits, for a particular change initiatives, are expected to be realised.
Beta
A phase of a project where the solution is in use and in the process of being improved, through testing within the Programme or in the public domain.
Also refers to the status of a Business Architecture Blueprint or artefact.
Blueprint
A Blueprint is a User Story level Business Architecture requirement and deliverable that describe a specific view or perspective of the Organisation. Blueprints make up HOBA® Business Architecture Building Blocks.
Building Blocks
Building Blocks are Epic level Business Architecture Requirements and deliverables. They are made up of Blueprints, that collectively describe a specific view or perspective of the Organisation. Building Blocks make up HOBA® Business Architecture Reference Models.
Business Architecture
In laments terms, How the Organisation is structured (architected) to execute its business strategy and achieve its Vision. In technical terms, a description of the structure and interactions between the Business Strategy, organisation, functions, business processes and information needs (source: TOGAF). Business Architecture makes up one half of an organisations Enterprise Architecture (the only half, and main domain is Technology Architecture. Also see Technology Architecture.
Business Architecture Approach (‘Approach’)
The high-level plan of the series of steps that are both required and followed in a specific and logical order to build up the Business Architecture.
Business Capability
In Business/Business Architecture context – a business capability is ‘what a business does’, made up of (essentially) people, process and technology. Each of these can be broken down further into people skills, culture, process steps, action, hardware, software, data etc.
Business Change/Business Changes
Changes that are needed or made to the business environment (people, skills, processes), to support the realisation of benefits (but excludes technology).
Note – business change implicitly includes culture, strategies/policies, practices, procedures as they are necessary to deliver the above mentioned ‘people’ and ‘process’.
Note – business change implicitly includes culture, strategies/policies, practices, procedures as they are necessary to deliver the above mentioned ‘people’ and ‘process’.