Skip to content

Reference & Data Model

Program (program)

A program bundles related projects of a portfolio and has its own phase, dates and budget goal.

A Program is an optional intermediate level between portfolio and project. It carries its own master details (lead, dates, budget goal, assessment) and rolls up the KPIs of its projects. (Data type: planning data, steering level)

Projekt & Portfolio › Projekte & Programme › Program › tab „Steckbrief“ (Fact sheet); phase via the phase label in the header. See Guides › Fact sheet, Guides › Lifecycle bar.

Field Technical Type Required Meaning Notes
Title name Text yes Program name
Key user_key Text yes Short unique code
Program manager leader_id Reference (Employee) yes (dialog) Main responsibility Technically optional
Type project_type_id Reference (Project type) no Project type of the program
Portfolio portfolio_id Reference yes Parent portfolio
Color color Selection yes Calendar/board color
Currency currency Selection yes Currency for the budget
Phase project_phase Selection yes Lifecycle phase Dialog „Phase wählen“ (Choose phase); new programs start in „Initialisierung“ (Initialization)
Budget goal budget_goal Amount no Planned total budget Own value, not a sum
Planned start target_start_date Date yes Planned program start
Planned end target_end_date Date yes Must be on or after the start
Actual start / end scheduled_start_at / scheduled_end_at Date no Under „Eckdaten“ (Key data) in the fact sheet System; currently not set by any process (stays „-“)
Success probability in % success_probability_in_pct Number no Assessment
Internal interest in % internal_interest_in_pct Number no Strategic significance / interest
General description description Text no „Beschreibende Daten“ (Descriptive data)
Program scope scope_description Text no Scope of delivery
Consequences of non-fulfillment consequences_of_non_fulfillment Text no
Specification specification_of_plant Text no Plant / requirements specification

Additionally computed in the fact sheet (system): „Wirtschaftlicher Nutzen“ (Economic benefit) = sum of the project benefits, „Priorisierung“ (Prioritization) = average of the projects’ priority ranks.

Related to Kind Required On archive On delete
Portfolio belongs to yes archived along (from the portfolio) blocked (portfolio not deletable)
Project type belongs to no kept reference cleared
Employee (lead) belongs to no kept reference cleared
Project has many – kept reference cleared (project stays in the portfolio)

Phases as for the project (see 3.3): Initialization, Definition, Planning, Execution, Closing. The program has no status and no lifecycle actions: the selection contains no end states, the phase is a free value and can be changed at any time. For the program there is no optimizer coupling: every chosen phase is saved directly.

  • A program without a portfolio cannot be saved; the „Updaten“ dialog reports a missing portfolio as a required field.
  • Deleting detaches the projects from the program instead of deleting them; archiving leaves the projects untouched.

Avg. progress, open tasks (rollup), K.O. criteria per project, program briefing: see Progress, Status, Counts.

Portfolio · Project · Guides › Setting up a program