Project Management Fundamentals — PMI vs Agile

The Split

Two fundamentally different assumptions

Project management has two dominant schools of thought, and they start from opposite assumptions about the nature of work. Understanding both isn't just academic: the wrong choice for a given project produces budget overruns, missed deadlines, or products nobody uses.

PMI / Predictive approach

Assumes requirements can be defined upfront
Plans the full scope before work begins
Change is controlled and managed through formal processes
Success = delivered on time, on budget, on scope
Works best when the destination is known

Building a bridge, migrating a data centre, implementing an ERP system.

Agile / Adaptive approach

Assumes requirements will evolve through discovery
Plans in short cycles, adapts continuously
Change is welcomed as a sign of learning
Success = value delivered to users, not plan adherence
Works best when the destination is uncertain

Building a new SaaS product, redesigning a customer app, running a marketing experiment.

PMI / PMBOK

The PMI approach: five process groups

The Project Management Institute (PMI) publishes the PMBOK Guide, the global standard for project management practice. It organises project work into five sequential process groups, each with defined inputs, tools, and outputs.

01

Initiating: Defining the project

Formally authorise the project, identify stakeholders, and define its high-level scope and objectives. Key outputs: Project Charter (the document that grants authority to the PM), Stakeholder Register. No project should begin without a signed charter. It prevents scope creep before work starts.

02

Planning: Defining how to get there

The most document-intensive phase. Outputs include: Work Breakdown Structure (WBS), Gantt chart schedule, resource plan, risk register, communication plan, and budget baseline. In PMBOK, planning is treated seriously. Changes to the plan later are costly. The project baseline (scope + schedule + cost) is locked here.

03

Executing: Doing the work

The team executes the plan. The PM coordinates resources, manages stakeholder communication, and resolves impediments. Quality assurance processes run throughout execution. Change requests, when they arise, are formally documented and evaluated against the project baseline before being approved or rejected.

04

Monitoring & Controlling: Tracking progress

Running in parallel with execution, M&C tracks performance against the baseline using Earned Value Management (EVM). Key metrics: Cost Performance Index (CPI), Schedule Performance Index (SPI). If CPI < 1, the project is over budget. If SPI < 1, it's behind schedule. Early detection allows corrective action before problems compound.

05

Closing: Formal completion

Obtain formal acceptance from the client or sponsor, archive project documents, release resources, and document lessons learned. The lessons learned register is the most consistently skipped step, and the most consistently regretted omission when the next project begins.

Core Concepts

The tools every PM needs to understand

Triple Constraint

Scope · Time · Cost: change one, you affect the others. Every project is constrained by scope (what gets built), time (when it's done), and cost (what it costs). Changing one affects at least one other. Adding scope without adding time or budget means quality suffers. Cutting budget without cutting scope means the timeline extends. The PM's job is to make these trade-offs explicit.

Work Breakdown Structure

Decompose the work until it's estimable. The WBS decomposes the project deliverables into smaller work packages, broken down hierarchically until each element is small enough to estimate, assign, and track. A well-built WBS is the foundation of the schedule and budget. A missing WBS is why estimates are always wrong.

Risk Register

Identify, assess, and respond before risks become issues. A risk register captures identified risks, their probability, potential impact, risk score (probability × impact), and the planned response (avoid, mitigate, transfer, accept). The goal is to move from reactive fire-fighting to proactive management. Most project failures were foreseeable risks that nobody acted on.

Stakeholder Management

Power/Interest grid: engage the right people, the right way. Plot stakeholders on a 2×2 grid: high power / high interest (manage closely), high power / low interest (keep satisfied), low power / high interest (keep informed), low power / low interest (monitor). Communication effort should be proportional to this grid, not equal for everyone.

Agile PM

Project management within Agile

In Agile environments, the PM role doesn't disappear. It transforms. Planning, tracking, and stakeholder management still happen, but with shorter cycles and more flexibility.

Rolling-wave planning

Plan in detail only what you can see clearly. Immediate sprints are fully planned; future sprints are estimated at a higher level (epics, story points). As the project evolves, detail is added progressively, not front-loaded into a plan that will inevitably change.

Velocity & forecasting

Agile teams track velocity (story points completed per sprint) to forecast when the backlog will be complete. After 3–4 sprints, velocity stabilises and provides a reliable release forecast, empirically grounded, not wishful thinking.

Servant leadership

In Scrum, the Scrum Master acts as a servant leader, removing impediments, facilitating ceremonies, and protecting the team from external interruptions. The PM role shifts from command-and-control to enablement and coaching.

Certifications

The main PM certifications

Certifications signal fluency in a methodology. They're not proof of good project management. They're proof that you understand the vocabulary and frameworks well enough to apply them.

PMP

Project Management Professional: PMI's flagship. The most globally recognised PM credential. Requires 36 months of project leadership experience, 35 hours of PM education, and a 180-question exam covering predictive, agile, and hybrid approaches. PMP holders command premium salaries across industries, particularly in construction, IT, finance, and consulting.

PRINCE2

Projects IN Controlled Environments: dominant in Europe and the UK. A process-based methodology originating with the UK government (now owned by PeopleCert). More prescriptive than PMBOK. It defines specific roles (Project Board, Project Manager, Team Manager) and management documents (PID, Business Case, Risk Register). Common in public sector, UK government contracts, and European enterprises.

PSM / CSM

Professional Scrum Master / Certified Scrum Master: Agile track. PSM I (Scrum.org) and CSM (Scrum Alliance) certify knowledge of the Scrum framework. Entry-level for Agile roles. PSM I is assessment-based (85% pass mark); CSM requires a 2-day course. For PM professionals moving into product or Agile roles, these are the fastest credential to signal the transition.

Hybrid

Most real projects are hybrid

The predictive vs. Agile debate is largely theoretical. In practice, most organisations blend both, using structured governance and fixed budgets from PMBOK with iterative delivery and cross-functional teams from Agile.

Watch out for these

Fixed scope, iterative delivery: The overall project scope and budget are fixed (PMI-style), but delivery happens in two-week sprints with demos and retrospectives (Agile-style). Common in enterprise IT implementations where procurement requires a fixed contract but the delivery team wants iterative feedback.

Agile delivery, waterfall governance: Product teams work in sprints with daily standups and sprint reviews, while reporting upward through PMO structures with quarterly status reports, budget variance analysis, and steering committee presentations. The team works Agile; the organisation governs waterfall.

Phased delivery with Agile execution: Large programs are divided into phases (Phase 1: MVP, Phase 2: Scale, Phase 3: Optimise). Each phase has a fixed budget and timeline agreed upfront. Within each phase, the team runs sprints. This gives sponsors the predictability they need while preserving team agility.

Takeaway

Choose the approach that fits the uncertainty

Certainty → PMI

When the requirements are clear, the technology is known, and the end state is well-defined, predictive planning pays off. The upfront investment in scope definition and risk planning prevents expensive rework later.

Uncertainty → Agile

When requirements will emerge through user feedback, when the technology is novel, or when the market is changing, Agile's short feedback loops reduce the cost of being wrong. You learn cheap rather than build expensively in the wrong direction.

Both → Hybrid

Most large organisations don't choose. They layer Agile delivery within PMI governance structures. Fluency in both frameworks makes you valuable in either environment, and the ability to translate between them is a genuinely rare skill.

ProjectManagementFundamentals