Initiate Project or Phase
Initiate Project or Phase formally authorizes a project or phase and gives the project manager authority to apply organizational resources to project work. Authorization—usually recorded in a Project Charter or equivalent—connects the project to its business case and the organization's strategic goals, records the decision, and demonstrates organizational commitment.
The approved business case explains why the project is being undertaken and the value it is expected to deliver. Initiation is usually performed once for a project, or again at selected life-cycle points such as phase boundaries. The timing depends on the development approach and the organization's governance. The project manager should be identified as early as possible, ideally while the charter is being developed and always before planning begins. The sponsor or project manager may develop the charter in collaboration with the initiating entity.
For a project involving multiple organizations, a contract establishes their agreement. Each organization can then use its project charter as an internal agreement to organize its responsibilities for meeting contractual obligations, such as contractor deliveries and customer payments.
Inputs, Tools & Techniques, and Outputs
| Inputs |
|
|---|---|
| Tools & Techniques |
|
| Outputs |
|
Initiation Activities
- Confirm the project's purpose, expected benefits, and connection to organizational strategy.
- Review the approved business case and relevant agreements, assumptions, constraints, risks, and environmental factors.
- Identify the sponsor, initiating entity, project manager, stakeholders, and initial responsibilities.
- Define the charter's objectives, high-level scope, authority, resource expectations, constraints, and approval conditions.
- Record assumptions and unresolved questions, and decide whether there is enough evidence to authorize the work.
- Approve, reject, defer, or request more evidence. Record the authorization and communicate the decision.
The charter creates an initial partnership between the requesting and performing organizations; it does not replace a contract when a contract is needed. It provides enough direction to authorize the project while leaving detailed planning to follow.
Adapt the Charter to the Development Approach
An adaptive project may use a concise worksheet or vision statement rather than a detailed charter. Tailor the level of detail to the project's uncertainty and governance needs: provide enough structure to align stakeholders while allowing requirements and priorities to evolve. An adaptive charter can answer some or all of these questions:
- Why is the project being undertaken?
- Who will be engaged?
- What is the project about?
- Where will it occur?
- When will it start and end?
- How will it be carried out?
- Who is the customer?
Governance check: Is there enough evidence to make a responsible commitment, is the project manager's authority clear, and is the person authorizing the work accountable for the exposure created?
Example: Authorizing a Phase
A phase review shows that the solution remains valuable, but a critical supplier has not demonstrated the required capability. The sponsor authorizes only the discovery work needed to validate alternatives, limits further commercial commitment, and sets a date for the next decision. Governance preserves momentum without pretending the full phase is ready.