project
Let an agent handle projects by objectives, scope, plan, risks, stakeholders and status, supporting structured project management.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle projects by objectives, scope, plan, risks, stakeholders and status, supporting structured project management.
A temporary, planned endeavour with defined objectives, scope, resources and timeframe to create a unique product, service or result, managed with methods such as waterfall, agile or PRINCE2.
What it is for: Delivering change and unique results.
It can be define objectives and scope; plan schedules and resources; track risks and issues; report status and close projects.
Distinguishing features
Temporary
Defined objectives
Unique output
Managed by methods
What it looks like
Not physical; plans, boards, documents and deliverables.
How it is recognised
Charters, plans and Gantt charts
Milestones and deliverables
Ongoing operations are not projects
Related models
is a kind of - category
is managed by - practice
produces - output
is part of - larger
In practice
Families and kinds
construction projects
software projects
research projects
megaprojects
cultural and heritage projects
Standards and regulation
ISO 21502 project management
PMBOK Guide
PRINCE2
Failure modes and hazards
Scope creep
Unrealistic schedules
Unmanaged risks
Also called
+131
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Definition Scope.
Scope must be clear.
Objectives
Goals.
Objectives
Objectives.
- What are the project objectives and success criteria? definition
- Who sponsors it? provenance
Scope
In and out.
Scope
Scope.
- What is in and out of scope? definition
- How are changes controlled? action
Plan Schedule.
Plans guide delivery.
Schedule
Milestones.
Schedule
Schedule.
- What are the milestones and critical path? measurement
- Are they realistic? boundary
Resources
Budget and people.
Resources
Resources.
- What budget and people are allocated? measurement
- Are they sufficient? boundary
Control Risks.
Risks must be managed.
Risks
Register.
Risks
Risk register.
- What are the top risks and mitigations? provenance
- Who owns each? provenance
Status
Reporting.
Status
Status reporting.
- Is the project on time, on budget and on scope? measurement
- What decisions are needed? action
Closure Ending.
Projects end.
Handover
Deliverables.
Handover
Handover.
- Have deliverables been accepted and handed over? boundary
- Who operates them now? provenance
Lessons
Review.
Lessons
Lessons learned.
- What lessons were learned? provenance
- How are they shared? action
What the second pass must settle
- Should project types be separate entries?
- How should project data be linked?
- How should programmes be modelled?