TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Work Package
Official definition — learn word for word
“A set of actions identified to achieve one or more objectives for the business. A work package can be a part of a project, a complete project, or a program.”
Source: CC §4.88
Memory aid
Work package = WORK (actions). Transition Architecture = a STATE you reach by doing the work.
Memory aid — not TOGAF wording.
In plain words
A bundle of work that closes one or more gaps and delivers something the business wants.
Plain-English summary — not TOGAF wording.
Worked example
“Integrate PayFlask with the new student record” is one work package; it could be a single project, or part of the larger Digital Campus program.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Work Package
SCOPE
Part of a project, a project, or a program
PHASE E · 9.3.9
Identify and group major work packages
PHASE F · 10.3.2
Assign a business value to each work package
IN THE ROADMAP
Work package portfolio on a timeline
GROUPED INTO
Portfolios and projects within a portfolio
NOT TO CONFUSE WITH
Transition Architecture (a state)
Source: CC §4.88 · ADM §9.3.9, §10.3.2 · AC §4.2.7
02Classifying current systems in Phase E · 9.3.9
| Class | Meaning |
|---|---|
| Mainstream | Part of the future information system |
| Contain | Expected to be replaced or modified in the planning horizon (next three years) |
| Replace | To be replaced in the planning horizon |
In the same step, fill the “Solution” column: new development, an existing product, or a solution that can be purchased (and in-house vs contract for new development).
Source: ADM §9.3.9
03Phase E · 9.3.9 Identify and Group Major Work Packages
Assess missing business capabilitiesfrom the Architecture Vision and Target Architecture
Group activities into work packagesusing the Consolidated Gaps, Solutions, and Dependencies matrix + Implementation Factor catalog
Recommend solution mechanismsnew development · existing product · purchase
Classify current systemsMainstream · Contain · Replace
Decompose into incrementsto deliver the capability increments
Group into portfolios and projectsconsidering dependencies and strategy
Source: ADM §9.3.9
04Where it appears in the ADM
Phase E · Step 9.3.9
Identify and Group Major Work Packages.
ADM §9.3.9
Phase F · Step 10.3.2
Assign a Business Value to Each Work Package.
ADM §10.3.2
05Exam traps
“A work package is always a single project” → Part of a project, a complete project, or a program
““Contain” means retire immediately” → Expected to be replaced or modified in the planning horizon (next three years)
“Business value is assigned in Phase E” → Phase F step 10.3.2
“Work packages are identified in Phase F” → Phase E step 9.3.9
06Self-test — tap to reveal
Q1Define a work package.
A set of actions identified to achieve one or more objectives for the business.
Q2What can a work package be?
Part of a project, a complete project, or a program.
Q3Which step identifies work packages?
Phase E step 9.3.9.
Q4Which inputs are used to group them?
The Consolidated Gaps, Solutions, and Dependencies matrix and the Implementation Factor catalog.
Q5Name the three system classifications.
Mainstream, Contain, Replace.
Q6What is the planning horizon mentioned?
The next three years.
Q7Which step assigns business value?
Phase F step 10.3.2.
Q8Where are work packages laid out on a timeline?
The Architecture Roadmap.