Landscape of projects, programs and portfolios
Support portfolio prioritization, funding and capacity decisions by exposing initiative dependencies, resource conflicts and attributable costs and benefits.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Delivery composition Reference distinct initiatives and their management relationships.
Delivery initiatives
Establish project identity and links to programmes, portfolios, products and teams.
Project identity
Distinguish an authorized project from a work tracking container.
- Which mandate, accountable owner and bounded outcome establish this record as a project?
- Which programmes and portfolio views reference this project?
Many-to-many links
Record product and team relationships without imposing exclusive membership.
- Which product records are linked to this project, and what role does each link express?
- Which team records are linked to this project, and what responsibility does each link express?
Dependencies and resources Assess resource contention and schedule dependencies within a dated planning basis.
Shared resources
Make capacity conflicts and their timing explicit.
Resource conflict
Relate initiative demand to the available capacity of a shared resource.
- Which initiative allocations exceed the available capacity of this resource during the stated period?
Schedule dependency
Assess a dependency against a specific schedule and milestone.
- Which predecessor and successor initiative commitments are connected by this dependency?
- Against which schedule version, target milestone and reporting date is this dependency assessed as critical or noncritical?
Delivery aggregation Produce totals that preserve the identity and attribution of underlying facts.
Allocation rules
Apply explicit cost and benefit allocation across overlapping views.
Single cost fact
Prevent repeated references from becoming duplicate financial contributions.
- Which allocation rule governs this cost fact's contribution to multiple views?
- What reconciliation demonstrates that this portfolio total counts no underlying fact twice through nested references?
- Which attribution rule governs this expected benefit when multiple initiatives claim it?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-05W1landscapeDeliveryLandscapeDeliveryScope
What it is Filled
Composition of management initiatives, dependencies, resources and expected benefits through self-contained objects.
Why it exists Filled
Support portfolio prioritization, funding and capacity decisions by exposing initiative dependencies, resource conflicts and attributable costs and benefits.
Distinguishing features Filled
- A container in a work tracker is not a project by itself.
- Projects, products and teams relate many-to-many and are composed by reference.
- Totals across views require an allocation rule so that a cost or benefit is counted once.
- Distinct from the strategic landscape, which links intents rather than delivery resources.
What robots and AI may and may not do Filled
Must not
- Sum budgets of all nested references, duplicates included, into a portfolio total.
- Treat a tracker container as a project without confirmation.
- Force project, product and team links into a single hierarchy.
- Reallocate shared resources between initiatives on its own initiative.
Only with a human decision
- Approving portfolio priorities and budgets.
- Resolving resource conflicts between initiatives.
May
- Build portfolio views from projects, products and teams by reference.
- Detect resource conflicts and double counted totals.
- Show the allocation rule behind every aggregated figure.
Moral aspects Filled
- Double counted benefits can justify investments that do not pay off.
- Resource conflicts resolved silently can overload the same people.
Who is affected
- Portfolio and programme managers
- Teams sharing resources
- Budget holders
Owners Filled
Steward
The portfolio management steward is accountable for the delivery landscape record, its composition rules and its aggregate reporting.
Master systems
- The initiative management system holds authoritative project, programme and portfolio records.
- The resource planning system holds authoritative capacity and allocation records.
- The financial management system holds authoritative cost and budget records.
- The benefits register holds authoritative expected benefits and attribution decisions.
- The product register holds authoritative product records.
- The team directory holds authoritative team records.
- The portfolio reporting register holds landscape membership, allocation rules and reporting snapshots.
Links to other meta-models Filled
references
- WM-ACT-029 - conceptual-candidate
- WM-ACT-005 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by the landscape identifier, the view purpose and the as-of date.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- Marked by initiatives, their many-to-many links and stated allocation rules.
- Often confused with a work tracker board or a budget spreadsheet.
Capabilities and actions required Filled
- One project can appear in several management views without duplication.
- Totals can be reproduced from single facts and allocation rules.
Hazards and failure modes required Filled
- Double counting of costs and benefits.
- Hierarchies that lose many-to-many links.
- Hidden over-allocation of shared people.
Standards and interfaces required Filled
- ISO 21502 guidance on project management.
- ISO 21504 guidance on portfolio management.
- ArchiMate by The Open Group for implementation and migration views.
Context of use required Filled
- Used for portfolio reviews, capacity planning and benefit tracking.
- Composed from work, product and team contours by reference.
Sources Filled
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
- The Open Group ArchiMate Forum - Checked live (HTTP 200) on 2026-10-07.
- The Open Group ArchiMate Overview - Checked live (HTTP 200) on 2026-10-07.
- Vercy Model Agent Protocol - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How does one project participate in several management views?
- Where does a shared resource create a conflict?
- How to rule out double counting of benefits?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-05/brief.json, ver-cy/world-models/card-supplements/em-lnd-05.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.