EM-LND-05 · Landscape · W1
Landscape of projects, programs and portfolios
Composition of management initiatives, dependencies, resources and expected benefits through self-contained objects.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- DeliveryLandscape
- DeliveryScope
Deep research 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?
Verifiable invariants
- A tracker container is not a project
- Project-Product-Team allows M:N
- Summation requires an allocation rule
End-to-end acceptance scenario
One project, two products and four teams preserve M:N and a single cost fact.
Negative case
A portfolio equals the sum of the budgets of all nested references, duplicates included.
Approaches to compare
- 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
Candidates in the live catalogue
- WM-ACT-029 · Program / Portfolio · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-005 · Project · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.