← Back to catalogue
Published

Program and Benefits Management

EM-WRK-03 · em-wrk-03

Coordinated projects and other work pursued for joint benefits, with management of the transition and the sustainability of the effect.

Enterprise profiles Enterprise subject EnterpriseWRK

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 9 questions

Program composition What the program groups and why grouping adds value.

Components

Projects and non-project work grouped in the program.

Program justification

The joint benefit that the components cannot deliver alone.

  1. Which joint benefit justifies grouping these components?
  2. Would the benefit be lost if the components were managed separately?

Component list

Each component with its type, owner and tranche.

  1. Which components belong to the program, including non-project work?
  2. Which tranche does each component belong to, and who owns its facts?
Benefits and transition How benefits are realised and sustained after delivery.

Benefits

Benefits and the dependencies that lead to them.

Benefit realisation

Evidence that a benefit was achieved, separate from project closure.

  1. Which benefits does the program target, and how is each measured?
  2. Which components does each benefit depend on?
  3. Has the benefit been achieved, or have only the projects closed?

Transition

Handover into operations and sustaining the effect.

Transition plan

The operational change that makes benefits durable.

  1. Which transition plan moves results into operation, and who receives them?
  2. Who is responsible for sustaining the benefit after the program closes?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseWRK
Industry
Cross-industry
Tags
EM-WRK-03W2subjectProgramProgramComponentTrancheBenefitDependencyTransitionPlan

What it is Filled

Coordinated projects and other work pursued for joint benefits, with management of the transition and the sustainability of the effect.

Why it exists Filled

Coordinated projects and other work pursued for joint benefits, with management of the transition and the sustainability of the effect.

Distinguishing features Filled

  • A program exists because coordinated work yields a joint benefit; a folder of unrelated projects is not a program.
  • Program components can include operational and transition work, not only projects.
  • The program owner coordinates but does not become the owner of every fact recorded by its projects.
  • Benefit realisation is measured on its own and may continue well after the projects have closed.

What robots and AI may and may not do Filled

Must not

  • Call an arbitrary grouping of unrelated projects a program.
  • Report a benefit as achieved because the projects behind it have closed.
  • Overwrite project facts on behalf of the program owner.
  • Drop non-project components from the program view.
  • Close a program without assigning responsibility for sustaining its benefits.

Only with a human decision

  • Establishing or closing a program.
  • Confirming that a benefit has been realised.
  • Approving a transition into operations.

May

  • List program components with their types, owners and tranches.
  • Trace each benefit to the components it depends on.
  • Report benefits whose measurement is missing or overdue.
  • Flag programs that lack a stated joint benefit.

Moral aspects Filled

  • Inflated benefit claims can misdirect investment and erode trust.
  • Transitions change how people work, so their effects on staff must be visible.

Who is affected

  • Program sponsors and funders
  • Staff affected by the transition
  • Beneficiaries of the program outcomes

Owners Filled

Steward

The project management office or program director who answers for program composition and benefits.

Master systems

  • Task tracker
  • Project portfolio management system
  • Plans and acceptance records

Links to other meta-models Filled

neighbor

  • EM-STR-02
  • EM-WRK-02
  • EM-WRK-04

references

  • WM-ACT-029 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by an organisational program code and mandate.
  • Components are identified by their own records and linked to the program with a tranche.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A program record names a joint benefit, components, tranches and a transition plan.
  • Often confused with a portfolio, a large project or a reporting folder.

Capabilities and actions required Filled

  • Benefit dependencies can be traversed from outcomes back to components.
  • Benefit realisation can be tracked after component closure.

Hazards and failure modes required Filled

  • Benefit double counting across overlapping programs.
  • Premature success claims based on project closure alone.
  • Orphaned benefits when nobody owns them after transition.

Standards and interfaces required Filled

  • ISO 21503 from ISO for guidance on programme management.
  • The Standard for Program Management from the Project Management Institute.
  • ISO 21508 from ISO for earned value management in projects and programmes.

Context of use required Filled

  • Used in organisational change, public sector programs and large transformations.
  • Benefits reviews often continue after formal program closure.

Sources Filled

  1. PMI: project/program/portfolio
  2. Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
  3. Tracker object practice: container, issue, workflow and binding to the business initiative
  4. ISO 21503:2022 Project, programme and portfolio management - Guidance on programme management - Carried over from the published world model wm-act-029-program-portfolio; checked live (HTTP 200) on 2026-10-09.
  5. ISO 21504:2022 Project, programme and portfolio management - Guidance on portfolio management - Carried over from the published world model wm-act-029-program-portfolio; checked live (HTTP 200) on 2026-10-09.
  6. ISO 21502:2020 Project, programme and portfolio management - Guidance on project management - Carried over from the published world model wm-act-029-program-portfolio; checked live (HTTP 200) on 2026-10-09.

Open questions

  • What additional benefit justifies grouping the work?
  • How are non-project components and benefit completion after the projects accounted for?
  • How is the Program discriminator of the existing WM-ACT-029 applied?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-wrk-03/brief.json, ver-cy/world-models/card-supplements/em-wrk-03.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.