Charter
DE: Projektauftrag
A document that formally authorizes a project and gives the PM authority.
Detailed Explanation
The project charter formally authorizes the project and provides the PM with authority to apply organizational resources. It is issued by the sponsor or an executive with sufficient authority.
Key elements: project purpose, measurable objectives, high-level requirements, budget, milestone schedule, stakeholder list, PM assignment with authority level, and key assumptions and constraints.
Created during the Initiating process group, the charter is the project's 'birth certificate.' It should be concise (1-3 pages) but give stakeholders a clear understanding of what will be accomplished and how the project will be governed.
Key Points
- Formally authorizes the project
- Issued by the sponsor, not the PM
- Defines PM authority and decision boundaries
- Includes high-level scope, budget, and timeline
- Created during project initiation
- References the business case
Practical Example
A CTO sponsors a cloud migration. The charter states: 'Migrate 50 apps to AWS within 18 months, budget EUR 1.5M, PM authorized for decisions up to EUR 50K.' It lists stakeholders, success criteria (99.9% uptime), and constraints (no business-hours downtime).
Tips for Learning and Applying
Keep it to 1-3 pages — details belong in the PM plan
Get the sponsor's signature — it is your authority document
Include measurable success criteria, not vague goals
Reference the business case for the strategic 'why'
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.