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.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 4 findings · 9 questions
Project definition The business project, its boundary and its relation to products and trackers.
Project and charter
A temporary undertaking authorised by a charter.
Project boundary
Start, end criteria and authorisation, independent of methodology.
- Which charter authorised the project, and what ends it?
- Which products and tracker containers does the project use, and are any shared with other projects?
Baseline and change The approved commitment, forecasts and changes to it.
Baseline
Approved scope, schedule and cost at a point in time.
Baseline versions
The original and each approved revision of the commitment.
- What did the original baseline commit to, and which revisions followed?
- Is a figure a forecast, an approved baseline value or an actual result?
Project change request
A request that changes the baseline when approved.
- Which change request altered the baseline, and who approved it?
- Does the change preserve the original commitment and its acceptance basis?
Delivery and acceptance Milestones, deliverables and their acceptance.
Milestones and deliverables
Points of progress and the results handed over.
Milestone status
A milestone reached by evidence, not by a closed task.
- What evidence shows the milestone was reached?
- Which deliverable was accepted, against which criteria and by whom?
- Does closing the project leave the product it changed in operation?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseWRK
- Industry
- Cross-industry
- Tags
- EM-WRK-02W1subjectProjectProjectCharterBaselineMilestoneDeliverable
What it is Filled
The business project, charter, plan, milestones, deliverables, acceptance and baseline changes. The product and the tracking system have separate identities.
Why it exists Filled
The business project, charter, plan, milestones, deliverables, acceptance and baseline changes. The product and the tracking system have separate identities.
Distinguishing features Filled
- A business project is a temporary undertaking with a charter; a tracker project is only a storage container.
- One project may use several tracker containers, and one container or product may serve several projects.
- A milestone is reached by evidence of progress, not by closing a task with the same name.
- Closing a project ends the undertaking while product identity remains independent, whether the project leaves a product in operation, decommissions one or is cancelled without delivering one.
What robots and AI may and may not do Filled
Must not
- Declare one tracker project to be one business project for its whole lifetime.
- Overwrite the original baseline when a change request is approved.
- Present a forecast as an approved commitment.
- Close the product record when the project is closed.
- Record a deliverable as accepted without the acceptance basis.
Only with a human decision
- Approving a project charter or a project change request.
- Formally accepting a deliverable.
- Closing a project.
May
- Link a project to its tracker containers and products in many-to-many form.
- Show forecast, baseline and actual values side by side with their sources.
- Trace each baseline revision to the change request that produced it.
- Flag milestones marked reached without supporting evidence.
Moral aspects Filled
- Silent baseline changes hide commitments made to customers, funders and staff.
- Accountability for delivery depends on keeping the original commitment visible.
Who is affected
- Project sponsors and funders
- Customers receiving deliverables
- Project team members
Owners Filled
Steward
The project management office or delivery lead who answers for project records and baselines.
Master systems
- Task tracker
- Project portfolio management system
- Plans and acceptance records
Links to other meta-models Filled
neighbor
- EM-FIN-01
- EM-KNW-02
- EM-PEO-02
- EM-RSK-02
- EM-STR-04
- EM-WRK-01
- EM-WRK-03
- EM-WRK-04
- EM-WRK-05
- EM-WRK-06
references
- WM-ACT-005 - conceptual-candidate
- WM-ACT-031 - conceptual-candidate
- WM-ACT-008 - conceptual-candidate
- WM-ACT-032 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by an organisational project code and charter, independent of tracker keys.
- Baselines are identified by project and revision number; deliverables by project and deliverable code.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A project record has a charter, a sponsor, a baseline and an end criterion.
- Often confused with a tracker container, a product or an ongoing operational process.
Capabilities and actions required Filled
- Variance can be computed between baseline, forecast and actual values.
- The history of commitments can be reconstructed from baseline revisions.
Hazards and failure modes required Filled
- Rewritten history when baselines are edited in place.
- Double counting when shared trackers or products are attributed to one project.
- Projects that never close because the tracker space stays active.
Standards and interfaces required Filled
- ISO 21502 from ISO for guidance on project management.
- The PMBOK Guide from the Project Management Institute.
- ISO 21508 from ISO for earned value management in projects and programmes.
Context of use required Filled
- Used wherever work is funded and governed as temporary projects, including client and internal projects.
- Change control matters most in fixed-price, regulated or publicly funded work.
Sources Filled
- 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
- The Scrum Guide - Checked live (HTTP 200) on 2026-10-07.
- UK Government Functional Standard GovS 002: Project Delivery - Checked live (HTTP 200) on 2026-10-07.
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-wrk-02/brief.json, ver-cy/world-models/card-supplements/em-wrk-02.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.