EM-WRK-02 · Subject model · W1
Project and Project Change Management
The business project, charter, plan, milestones, deliverables, acceptance and baseline changes. The product and the tracking system have separate identities.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Project
- ProjectCharter
- Baseline
- Milestone
- Deliverable
- Acceptance
- ProjectChangeRequest
Deep research questions
- How is a project's temporal boundary defined without mandating a waterfall methodology?
- How do many-to-many relationships between projects, products and tracker containers work?
- How are a forecast, an approved baseline and an actual result distinguished?
Verifiable invariants
- A project may have several tracker containers
- A milestone is not a completed task
- Closing a project does not close the product
End-to-end acceptance scenario
Two projects share one tracker and one product; a change request changes the baseline while preserving the original commitment and the acceptance basis.
Negative case
One Jira Project is declared one business project for all the years of its existence.
Approaches to compare
- PMI: project/program/portfolio
- Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
- Tracker object practice: container, issue, workflow and binding to the business initiative
Candidates in the live catalogue
- 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. - WM-ACT-031 · Milestone / Deliverable · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-008 · Plan / Schedule · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ACT-032 · Change Request · 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.