The Five Project Phases
Every project, regardless of methodology, follows a lifecycle with distinct phases. Understanding these phases helps you know where you are, what is expected, and what comes next. The five universally recognized phases are: Initiation, Planning, Execution, Monitoring & Control, and Closing.
In Waterfall, these phases are sequential. In Agile, Planning, Execution, and Monitoring overlap within each sprint. But the high-level lifecycle remains the same regardless of approach.
Phase 1: Initiation
The project is formally authorized and defined at a high level. This is where you answer the question: "Should we do this project?"
- Key Activities: Define business case, identify stakeholders, assess feasibility, appoint project sponsor and PM
- Key Deliverables: Project charter, stakeholder register, preliminary scope statement
- Phase Gate: Sponsor approval of the project charter (go/no-go)
- Common Pitfall: Skipping the charter and jumping straight into planning without formal authorization
Phase 2: Planning
The most critical phase. Comprehensive plans are created for scope, schedule, cost, quality, resources, communications, risk, and procurement.
- Key Activities: Create WBS, develop schedule, estimate costs, plan risk responses, define quality standards, plan communications
- Key Deliverables: Project management plan, WBS, schedule baseline, cost baseline, risk register, communication plan
- Phase Gate: Baseline approval by sponsor and key stakeholders
- Common Pitfall: Under-planning (winging it) or over-planning (analysis paralysis)
Phase 3: Execution
The team performs the work defined in the project plan. This is where the bulk of the budget is spent and the deliverables are produced.
- Key Activities: Direct and manage project work, acquire and develop the team, manage stakeholder engagement, conduct procurements
- Key Deliverables: Working software increments, project status reports, team performance assessments
- Phase Gate: Deliverable acceptance and milestone reviews
- Common Pitfall: Not following the plan, scope creep without change control
Phase 4: Monitoring & Control
Running in parallel with execution, this phase tracks progress, manages changes, and takes corrective action when the project deviates from the plan.
- Key Activities: Track KPIs, perform variance analysis, manage change requests, monitor risks, control quality
- Key Deliverables: Performance reports, change log, updated risk register, earned value reports
- Phase Gate: Performance review gates, stage-gate approvals for next phase
- Common Pitfall: Ignoring early warning signs, not acting on variance data
Phase 5: Closing
The project is formally completed, deliverables are handed off, and lessons learned are documented.
- Key Activities: Obtain final acceptance, release resources, close contracts, conduct retrospective, archive documents
- Key Deliverables: Final project report, lessons learned document, archived project artifacts
- Phase Gate: Formal sign-off from sponsor and stakeholders
- Common Pitfall: Skipping the retrospective, not documenting lessons learned
Phase Gate (Stage Gate) Process
Phase gates are decision points where the project is evaluated before proceeding to the next phase. At each gate, stakeholders review progress and decide: Go (proceed), No-Go (stop the project), or Recycle (redo parts of the current phase).
// Phase Gate Decision Model
interface PhaseGate {
phase: string;
gateName: string;
criteria: GateCriterion[];
decision: 'go' | 'no-go' | 'recycle' | 'pending';
reviewDate: Date;
reviewers: string[];
}
interface GateCriterion {
name: string;
description: string;
status: 'met' | 'partially-met' | 'not-met';
evidence: string;
weight: number; // 1-5, used for scoring
}
const initiationGate: PhaseGate = {
phase: 'Initiation',
gateName: 'Gate 1: Project Authorization',
criteria: [
{
name: 'Business Case Approved',
description: 'ROI analysis shows positive return within 18 months',
status: 'met',
evidence: 'Business case document v1.2 approved by CFO',
weight: 5
},
{
name: 'Stakeholders Identified',
description: 'All key stakeholders identified and documented',
status: 'met',
evidence: 'Stakeholder register with 12 stakeholders',
weight: 3
},
{
name: 'Budget Available',
description: 'Funding confirmed for planning phase',
status: 'met',
evidence: 'Finance approval email from VP Finance',
weight: 5
},
{
name: 'Strategic Alignment',
description: 'Project aligns with organizational strategy',
status: 'met',
evidence: 'Mapped to strategic objective SO-3',
weight: 4
},
{
name: 'Resource Availability',
description: 'Key resources available for project timeline',
status: 'partially-met',
evidence: 'Lead architect available Q2, need to backfill current role',
weight: 3
}
],
decision: 'go',
reviewDate: new Date('2024-03-15'),
reviewers: ['VP Engineering', 'Product Director', 'CFO']
};
// Calculate gate score
function calculateGateScore(gate: PhaseGate): {
score: number;
maxScore: number;
percentage: number;
recommendation: string;
} {
let score = 0;
let maxScore = 0;
for (const criterion of gate.criteria) {
maxScore += criterion.weight * 2;
if (criterion.status === 'met') score += criterion.weight * 2;
else if (criterion.status === 'partially-met') score += criterion.weight;
}
const percentage = (score / maxScore) * 100;
return {
score,
maxScore,
percentage,
recommendation: percentage >= 80 ? 'GO' : percentage >= 60 ? 'CONDITIONAL GO' : 'NO-GO'
};
}Effort Distribution Across Phases
Not all phases consume equal effort. Understanding the typical effort distribution helps with resource planning and expectations.
| Phase | Effort % | Cost % | Duration % | Primary Focus |
|---|---|---|---|---|
| Initiation | 2-5% | 1-3% | 5-10% | Define and authorize |
| Planning | 10-20% | 5-15% | 15-25% | Create comprehensive plan |
| Execution | 50-60% | 60-75% | 40-50% | Build deliverables |
| Monitoring | 15-25% | 10-15% | Parallel | Track and control |
| Closing | 5-10% | 3-5% | 5-10% | Formalize completion |
Adapting Phases for Agile
In Agile projects, the lifecycle phases still exist but they compress and repeat within each iteration:
Agile Phase Mapping
- Initiation: Happens once at project start (create product vision, initial backlog, team formation)
- Planning: Repeats each sprint (sprint planning) and at release level (release planning)
- Execution: Repeats each sprint (daily development, integration, testing)
- Monitoring: Continuous (daily standups, burndown tracking, sprint review)
- Closing: Sprint retrospective (mini-closing) + final project closing
Real-World Example: E-Commerce Platform Rewrite
// Project lifecycle for an e-commerce rewrite
const ecommerceRewrite = {
initiation: {
duration: '2 weeks',
activities: [
'Business case: current platform costs $500K/yr in maintenance',
'Stakeholder analysis: 15 stakeholders identified',
'High-level scope: rewrite checkout, product catalog, search',
'Budget estimate: $1.2M over 12 months',
'Charter approved by CTO and VP Product'
],
gate: 'Charter signed, budget allocated'
},
planning: {
duration: '6 weeks',
activities: [
'Detailed requirements gathering (120 user stories)',
'Architecture design (microservices, event-driven)',
'WBS created (450 work packages)',
'Schedule: 10 sprints over 5 months',
'Risk register: 28 risks identified',
'Team: 2 squads of 6 engineers each'
],
gate: 'Baselines approved, team onboarded'
},
execution: {
duration: '5 months (10 sprints)',
activities: [
'Sprint 1-2: Core infrastructure, CI/CD, auth service',
'Sprint 3-4: Product catalog service, search (Elasticsearch)',
'Sprint 5-6: Shopping cart, checkout flow',
'Sprint 7-8: Payment integration, order management',
'Sprint 9-10: Performance tuning, migration scripts, UAT'
],
gate: 'Each sprint: demo and stakeholder acceptance'
},
monitoringAndControl: {
continuous: true,
activities: [
'Daily standups and blocker resolution',
'Sprint velocity tracking (target: 45 points/sprint)',
'Budget burn rate monitoring (weekly)',
'Risk reviews (bi-weekly)',
'Change requests processed through CCB'
]
},
closing: {
duration: '3 weeks',
activities: [
'Final UAT sign-off from business stakeholders',
'Production cutover (blue-green deployment)',
'Old system decommission plan',
'Team retrospective and lessons learned',
'Final project report to steering committee',
'Team celebration and resource release'
],
gate: 'Sponsor sign-off, go-live confirmed'
}
};