Project Management Framework

Evidence and source status

Source-fidelity note: This handbook preserves the supplied source's concepts while making their application explicit. Unless directly supported by an authoritative reference below, numerical values, schedules, counts, ratios, named frameworks, market or salary claims, thresholds and case-study details are source examples or source viewpoints—not universal standards, forecasts or mandatory requirements. Case narratives and allegations have not been independently adjudicated and are presented for learning, not as findings of fact. Verify current legislation, contracts, professional obligations and organisation-specific limits before relying on the material.

Overview

Project management is a structured framework for taking any initiative from conception to completion with a 100% goal achievement rate. It applies universally — whether hiring, launching campaigns, building products, or executing any business initiative. Mastering this framework ensures projects are delivered on time, within scope, and within budget.

Key Concepts

• Project – A temporary endeavour undertaken to create a unique product, service, or result
• Project Management – The application of knowledge, skills, tools, and techniques to project activities to meet project requirements
• Temporary vs. Ongoing – A project has a defined start and end; ongoing activities (e.g., routine hiring) are operations, not projects
• Five Pillars – Initiation, Planning, Execution, Monitoring & Controlling, Closing
• Ten Success Factors – Integration, Scope, Time, Cost, Procurement, Human Resources, Communications, Delay Management, Risk Management, Stakeholder Management

Detailed Notes

Defining a Project

• A project is distinct from day-to-day operations because it is temporary and produces a unique outcome
• If an activity is ongoing and repetitive, it is an operation, not a project
• If an activity has a defined objective and endpoint, it qualifies as a project
  • e.g., "Hire a senior executive" = project (ends when the hire is made)
  • e.g., "Ongoing recruitment" = operation (continuous, no fixed end)

The Five Pillars of Project Management

1. Initiation

• The phase where a project is conceived and defined
• A need or opportunity is identified
• The project's purpose and feasibility are evaluated before committing resources

2. Planning

• A detailed plan is created covering scope, timeline, resources, and deliverables
• The right team is assembled based on the project's requirements
• Key decisions are made about who will execute, how it will be done, and when milestones must be hit

3. Execution

• The plan is put into action
• Tasks are assigned, resources are deployed, and deliverables are produced
• Multiple activities may run in parallel across the project timeline
• Includes ancillary tasks (onboarding, payments, documentation, etc.)

4. Monitoring and Controlling

• Ongoing oversight to ensure the project is on track with the plan
• Identify gaps between planned vs. actual progress
• Adapt to unexpected disruptions (market shifts, crises, resource loss)
• Senior leaders should own accountability for end-to-end execution with no time gaps
• The founder or business owner should act as the chief oversight authority, ensuring all project managers report progress consistently

5. Closing

• The project is formally completed with 100% of objectives achieved
• Accounts for changes that occurred mid-project (scope changes, new factors, timeline shifts)
• A strong project manager handles extensions, cost changes, and resource adjustments without losing control
• Final deliverables are reviewed, accepted, and the project is formally closed

Ten Steps to Successful Project Management

1. Integration

• Ensure the project fits within the broader business context
• Avoid tunnel vision — do not let one project consume all attention at the expense of overall business growth
• Balance project focus with ongoing operations

2. Scope

• Clearly define the boundaries and deliverables of the project
• The project manager's key responsibility area (KRA) is managing scope
• Prevents scope creep (uncontrolled expansion of project requirements)

3. Time

• Establish a clear timeline for delivery
• Estimate how long each phase and task will take
• Time overruns directly impact cost and stakeholder confidence

4. Cost

• Budget must account for all project expenses:
  • Human resource cost (salaries, contractors)
  • Operational cost (infrastructure, logistics)
  • Technical cost (tools, software, equipment)
• Funds are allocated to the project manager based on scope, team size, and timeline

5. Procurement

• Acquire everything needed for project success:
  • Raw materials
  • Human resources
  • Communication infrastructure
  • Funding
• Procurement delays can stall the entire project

6. Human Resources

• Determine how many people are needed
• Identify the skill sets required
• Decide the cost level of talent to deploy
• Right-sizing the team is critical — too few causes delays, too many inflates cost

7. Communications

• Small teams (2–3 people) → communication is straightforward
• Large teams (hundreds or thousands) → communication becomes a major challenge
• The project manager must define:
  • KPIs (Key Performance Indicators)
  • KRAs (Key Result Areas)
  • Communication cadence and channels

8. Delay Management

• Project extensions increase cost and reduce stakeholder trust
• Proactively manage timelines to prevent slippage
• Build buffer time into plans for foreseeable delays

9. Risk Management

• Identify potential risks from Day 1:
  • Key team members leaving mid-project
  • Communication breakdowns
  • External disruptions (natural disasters, economic shifts)
  • Funding shortfalls
• Develop contingency plans for each identified risk
• Risk-aware project managers prevent small issues from becoming project-ending crises

10. Stakeholder Management

• Internal stakeholders – employees, team members, leadership
• External stakeholders – customers, partners, retailers, distributors, investors, and (for public companies) the general public
• Consistent communication and expectation management across all stakeholder groups is essential

Tables

Five Pillars of Project Management

Ten Success Factors at a Glance

Diagrams

Project Management Lifecycle

Source process map

1. 1Initiation
2. 2Planning
3. 3Execution
4. 4Monitoring & Controlling
5. 5Closing
6. 6100% Goal Achievement

Sequence reconstructed as accessible HTML from the supplied text diagram. Review branch conditions against the surrounding source explanation.

Ten Success Factors – Concept Map

Source process map

1. 1Project Management Success
2. 2Integration
3. 3Scope
4. 4Time
5. 5Cost
6. 6Procurement
7. 7Human Resources
8. 8Communications
9. 9Delay Management
10. 10Risk Management
11. 11Stakeholder Management

Sequence reconstructed as accessible HTML from the supplied text diagram. Review branch conditions against the surrounding source explanation.

Risk Management Process

Source process map

1. 1Day 1: Identify Potential Risks
2. 2Assess Likelihood & Impact
3. 3Develop Contingency Plans
4. 4Monitor Throughout Project
5. 5Risk Event Occurs?
6. 6Activate Contingency Plan
7. 7Adapt & Continue Execution

Sequence reconstructed as accessible HTML from the supplied text diagram. Review branch conditions against the surrounding source explanation.

Key Terms

• Project – A temporary endeavour with a defined start and end, producing a unique output
• Project Management – Applying knowledge, skills, tools, and techniques to meet project requirements
• Initiation – The phase where a project idea is conceived and evaluated
• Scope – The defined boundaries and deliverables of a project
• Scope Creep – Uncontrolled expansion of project requirements beyond the original plan
• KPI (Key Performance Indicator) – A measurable value that tracks performance against objectives
• KRA (Key Result Area) – A defined area of accountability tied to a specific role
• Procurement – The process of acquiring resources (materials, people, funding) needed for the project
• Risk Management – Identifying, assessing, and preparing for potential threats to project success
• Stakeholder – Any party (internal or external) with an interest in the project's outcome
• Integration – Ensuring the project aligns with and fits within the broader business strategy

Quick Revision

1. A project is a temporary endeavour with a unique output — distinct from ongoing operations.
2. Project management applies knowledge, skills, tools, and techniques to meet project goals.
3. The five pillars are: Initiation → Planning → Execution → Monitoring & Controlling → Closing.
4. Integration ensures the project fits within the overall business without consuming all resources.
5. Scope, Time, and Cost form the classic "triple constraint" — changes to one affect the others.
6. Procurement covers acquiring all resources (materials, people, funding, infrastructure).
7. Communication complexity scales with team size — large teams require structured channels and clear KPIs/KRAs.
8. Risk management starts on Day 1 — identify risks early, build contingency plans, monitor continuously.
9. Delay management is proactive — extensions increase cost and erode stakeholder confidence.
10. Stakeholder management spans internal (employees) and external (customers, partners, investors) groups — consistent communication is essential.

Application framework

Treat Project Management Framework as a managed business practice rather than a one-off activity. Begin by defining the outcome, the decision owner and the boundary of the work. Then identify which source concepts are most relevant: Defining a Project, The Five Pillars of Project Management, 1. Initiation and 2. Planning. The concepts are connected, but they should not be treated as interchangeable. Each answers a different question about what to do, why it matters or how evidence will be judged.

Use a simple cycle: frame the issue, gather evidence, choose an approach, implement it, observe the result and capture what was learned. This makes the practice repeatable and gives reviewers a clear trail from an initial assumption to an operational decision. A small organisation can use a one-page record; a larger organisation may distribute the same fields across existing planning, risk and performance systems.

Before proceeding, state what is outside scope. An explicit boundary prevents a useful method from being extended into legal, financial, employment or technical advice that the source does not support. Where a decision depends on regulation, a contract or a professional judgement, verify that dependency separately.