🌿The Ultimate Project Management Jargon Lexicon
🌿Projects vs Operations in Project Management - Key Differences and Examples
🌿Project Risk Management - A Comprehensive Guide to Identifying and Managing Project Threats
The project management life cycle comprises five distinct phases (Process Groups) defined by the Project Management Institute (PMI): Initiation, Planning, Execution, Monitoring & Controlling, and Closing. Each phase acts as a structural gateway containing specific core activities, execution milestones, and foundational artifacts. Transitioning safely from one phase to the next requires the formal approval and signing of designated exit-gate documents to prevent scope creep, misaligned budgets, and delivery failure. [1]
View Business English Lesson on StudyESL.ca
Project Management Lifecycles & Gate Deliverables
1. Project Initiation Phase
The starting line where a project's strategic alignment, high-level scope, and overall viability are evaluated before being officially authorized. [2]
Core Objectives: What Needs to Be Completed
-
Identify the core business need: Frame the primary problem or opportunity the project addresses and verify that its execution supports the organization's overarching strategy. [1:1]
-
Establish high-level boundaries: Estimate the project's preliminary budget, expected timeline, and high-level constraints. [2:1]
-
Identify key stakeholders: Perform an initial analysis of individuals, departments, or clients impacted by or involved in the project. [1:2]
-
Appoint the Project Manager (PM): Formally assign the PM and outline their level of authority to commit organizational resources. [3]
Gateway Deliverables: Critical Documentation for Completion
-
Business Case: A comprehensive justification detailing the cost-benefit analysis, strategic alignment, and potential return on investment (ROI). [4]
-
Feasibility Study: An assessment analyzing technical, economic, legal, and operational viability to confirm the project can be completed. [4:1]
-
Project Charter (Primary Gate Document): The formal authorization document that defines high-level objectives, key stakeholders, high-level scope, and PM authority. Signing this officially transitions the project to the planning phase. [2:2] [3:1]
-
Initial Stakeholder Register: A preliminary log detailing the names, roles, expectations, and influence levels of key stakeholders. [1:3]
2. Project Planning Phase
The intellectual heavy lifting where the roadmap is drawn. This phase maps out the detailed execution, resource requirements, timelines, risk mitigations, and budget baselines. [1:4]
Core Objectives: What Needs to Be Completed
-
Deconstruct the scope: Break down the overall scope into granular, manageable work items. [2:3]
-
Develop the schedule: Formulate logical task dependencies, estimate effort, assign resources, and establish milestone deadlines. [2:4]
-
Baseline the budget: Aggregate cost estimates across tasks to define the total spending baseline. [3:2]
-
Establish risk and quality plans: Proactively identify project risks, analyze their impact, construct mitigation strategies, and define quality benchmarks. [2:5]
Gateway Deliverables: Critical Documentation for Completion
-
Work Breakdown Structure (WBS) & WBS Dictionary: A visual deconstruction of the project's entire scope into specific deliverables and task packages. [2:6]
-
Project Schedule (Gantt Chart / Critical Path): A detailed timeline containing task dependencies, milestones, and critical pathways. [2:7]
-
Resource Management Plan: A document establishing the staffing, equipment, and material allocations needed across tasks. [2:8]
-
Risk Register: A live matrix mapping identified risks, their probability/impact, mitigation strategies, and risk owners. [2:9]
-
Project Management Plan (PMP) (Primary Gate Document): The master roadmap consolidating the Scope Statement, Schedule Baseline, Cost Baseline, and subsidiary plans (Change Control, Quality, and Communication). Approved and signed off by the sponsor before execution begins. [3:3]
3. Project Execution Phase
The action phase where plans are translated into physical or digital assets. Most of the budget and resources are consumed here as the project team builds out the primary deliverables. [1:5]
Core Objectives: What Needs to Be Completed
-
Mobilize the project team: Onboard, train, and manage team members, ensuring everyone understands their roles (often utilizing a RACI matrix). [4:2]
-
Build deliverables: Execute the tasks defined in the Project Management Plan to produce the final products or services. [4:3]
-
Manage communications: Deliver regular updates to team members and key stakeholders according to the communication plan. [1:6]
-
Manage procurements: Acquire and manage external vendor deliverables, services, or materials. [3:4]
Gateway Deliverables: Critical Documentation for Completion
-
Working Project Deliverables (The Product/Service): The actual output (e.g., code repository, physical structure, system migration). [4:4]
-
Work Performance Data: Raw measurements of task progress, actual costs incurred, and actual start/end dates. [3:5]
-
RACI Matrix: A finalized matrix establishing who is Responsible, Accountable, Consulted, and Informed for each deliverable. [4:5]
-
Procurement Documentation & Vendor Agreements: Completed, signed contracts with external suppliers and material receipts. [2:10]
4. Project Monitoring & Controlling Phase
Running concurrently with the Execution phase, this is the feedback loop. The PM constantly measures progress against the baseline, correcting course and managing changes to prevent drift. [1:7]
Core Objectives: What Needs to Be Completed
-
Track key performance metrics (KPIs): Compare actual scope, schedule, and cost performance against the established baselines. [1:8]
-
Manage scope creep: Mitigate unsanctioned additions to project scope and ensure any changes undergo a formal review process. [2:11]
-
Control quality: Verify that project deliverables meet the specifications outlined in the quality management plan. [2:12]
-
Manage issues and change requests: Document issues as they arise and submit formal proposals for scope, cost, or schedule changes. [2:13]
Gateway Deliverables: Critical Documentation for Completion
-
Project Status Updates & KPI Dashboards: Regular, visual performance updates (often using Earned Value Analysis for schedule/cost variances). [3:6] [5]
-
Issue Log: A centralized tracker detailing active obstacles, priority, assignees, and resolution statuses. [5:1]
-
Change Requests & Change Control Log: Formally submitted documentation requesting plan alterations, paired with a tracking log displaying approval/rejection status. [2:14] [5:2]
-
Quality Audit Reports & QA Checklists: Signed check-offs proving deliverables meet defined quality thresholds. [4:6]
5. Project Closure Phase
The final gateway where deliverables are handed off, contracts are wrapped up, resources are released, and institutional knowledge is archived. [1:9]
Core Objectives: What Needs to Be Completed
-
Transition deliverables: Hand over the final products or services to the operations team, client, or end-user. [4:7]
-
Finalize contracts: Resolve open issues with vendors, pay outstanding invoices, and formally close contracts. [3:7]
-
Release resources: Return team members, equipment, and remaining budget back to the organization or parent department. [3:8]
-
Conduct post-mortem review: Gather the team to discuss what went well, what failed, and how processes can be optimized for future endeavors. [3:9]
Gateway Deliverables: Critical Documentation for Completion
-
Formal Project Sign-off / Acceptance Document: A legally binding document signed by the client or project sponsor declaring the project meets criteria and is officially accepted. [5:3]
-
Project Closure Report (Primary Gate Document): A final report detailing budget variance, schedule variance, final output metrics, and contract closeout documentation. [3:10]
-
Lessons Learned Register: A searchable knowledge repository documenting historical challenges, solutions, and strategic insights to improve future project performance. [3:11]
-
Archived Project Repository: The organized filing away of all project-related emails, blueprints, codebases, plans, and technical documentation. [5:4]
References
Marianne Sison / Project Life Cycle: The 5 Phases Explained for Modern Teams / project-management.com ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Visual Paradigm / 5 Phases of Project Management [PMBOK Version] / Visual Paradigm Guides ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
ProjectEngineer / The PMBOK's Five Project Phases / ProjectEngineer ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
QRP International / 5 Process Groups in PMP - Project Management / QRP International ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Sonoma State University IT / What are the key deliverables of the project management process? / Sonoma State University KB ↩︎ ↩︎ ↩︎ ↩︎ ↩︎