Wiki.Quizz.vn

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Predictive vs Agile ======

===== Introduction =====

One of the most important modern PMP topics is understanding:

> Predictive vs Agile

Many learners assume:

Predictive and Agile are competitors.

This is misleading.

PMP teaches:

> Different projects need different approaches.

The question is usually not:

"Which is universally better?"

Instead:

> Which approach best fits the project context?

Understanding this difference helps teams:

  * choose appropriate planning style
  * manage uncertainty
  * improve delivery
  * align with stakeholder expectations

Modern project management values adaptability.

Not ideology.

-----

===== What is Predictive? =====

Predictive is often called:

> Waterfall

Predictive project management assumes:

Most requirements can be understood and planned early.

Therefore:

Planning happens heavily upfront.

Execution follows approved plan.

Basic flow:

```text
Requirements
    ↓
Planning
    ↓
Design
    ↓
Build
    ↓
Test
    ↓
Release
```

Progress moves sequentially.

Changes are managed carefully.

Predictive emphasizes:

  * predictability
  * control
  * upfront planning
  * documentation
  * governance

-----

===== Predictive Characteristics =====

Typical characteristics:

  * defined scope early
  * detailed schedule
  * formal approvals
  * controlled change
  * milestone-based delivery
  * extensive planning

Goal:

Reduce uncertainty through planning.

-----

===== Predictive Example =====

Construction project.

Building bridge.

Before construction:

Need:

  * engineering design
  * permits
  * budget approval
  * material planning

Constant redesign is expensive.

Predictive works well.

-----

===== Software Predictive Example =====

Example:

Government tax system.

Requirements:

  * regulatory rules
  * compliance controls
  * fixed deadlines
  * heavy audit requirements

Predictive may fit.

Why?

Requirements relatively stable.

Governance important.

-----

===== Advantages of Predictive =====

Predictive offers several strengths.

===== High Predictability =====

Because planning is detailed:

Stakeholders gain visibility.

Questions easier to answer:

  * cost
  * timeline
  * milestones

Predictability improves confidence.

-----

===== Strong Governance =====

Predictive provides:

  * approvals
  * documentation
  * audit trail
  * decision checkpoints

Useful in regulated environments.

-----

===== Scope Stability =====

Scope defined early.

This reduces:

  * uncontrolled change
  * delivery confusion
  * requirement drift

Control improves.

-----

===== Weaknesses of Predictive =====

Predictive also has limitations.

===== Less Flexible =====

Late changes may be costly.

Problem:

Reality evolves.

Rigid plans may struggle.

-----

===== Slow Feedback =====

Users may see results late.

Risk:

Wrong assumptions discovered too late.

-----

===== Heavy Planning Overhead =====

Detailed planning requires:

  * time
  * meetings
  * documentation

Useful sometimes—

excessive in others.

-----

===== What is Agile? =====

Agile takes a different approach.

Agile assumes:

Requirements and solutions evolve.

Therefore:

Planning and delivery occur iteratively.

Basic Agile cycle:

```text
Plan
 ↓
Build
 ↓
Review
 ↓
Adapt
 ↺
```

Small increments.

Continuous feedback.

Agile emphasizes:

  * adaptability
  * customer collaboration
  * iterative delivery
  * learning
  * responsiveness

Agile embraces uncertainty.

Rather than trying to eliminate it completely.

-----

===== Agile Characteristics =====

Typical characteristics:

  * iterative work
  * incremental delivery
  * evolving requirements
  * customer feedback
  * self-organizing teams
  * adaptive planning

Goal:

Learn and adapt rapidly.

-----

===== Agile Example =====

Startup mobile app.

Requirements uncertain.

Need:

  * experimentation
  * customer feedback
  * rapid iteration

Predictive planning may fail.

Agile fits better.

Why?

Product learning matters.

-----

===== Software Agile Example =====

Example:

New SaaS platform.

Unknown:

  * feature demand
  * UX preference
  * adoption pattern

Agile approach:

Sprint 1:

Basic MVP.

Sprint 2:

Review usage.

Sprint 3:

Adjust priorities.

This reduces waste.

-----

===== Agile Advantages =====

Agile provides several strengths.

===== Flexibility =====

Requirements can evolve.

This improves responsiveness.

Change becomes manageable.

Not catastrophic.

-----

===== Faster Feedback =====

Users see value earlier.

Feedback appears sooner.

Risk reduces.

Because assumptions validated earlier.

-----

===== Customer Collaboration =====

Agile emphasizes:

Continuous involvement.

Stakeholders shape solution.

This increases alignment.

-----

===== Continuous Improvement =====

Teams learn continuously.

Retrospectives improve:

  * process
  * communication
  * delivery quality

Improvement becomes routine.

-----

===== Agile Weaknesses =====

Agile also has trade-offs.

===== Lower Predictability =====

Because scope evolves:

Exact timeline and cost may be harder to forecast.

Some organizations find this uncomfortable.

-----

===== Requires Strong Collaboration =====

Agile depends on:

  * communication
  * trust
  * engagement

Weak collaboration harms Agile effectiveness.

-----

===== Risk of Scope Expansion =====

Without discipline:

Agile may experience:

  * endless iteration
  * shifting priorities
  * unclear completion

Agile still needs management.

-----

===== Predictive vs Agile Comparison =====

High-level comparison:

| Area | Predictive | Agile |
| --- | --- | --- |
| Planning | Heavy upfront | Iterative |
| Scope | Defined early | Evolves |
| Change | Controlled | Expected |
| Delivery | Large release | Incremental |
| Feedback | Later | Early |
| Predictability | Higher | Lower |
| Flexibility | Lower | Higher |
| Governance | Strong | Lightweight |
| Best for | Stable work | Uncertain work |

Neither is automatically superior.

Context matters.

-----

===== Hybrid Approach =====

Modern PMP strongly supports:

> Hybrid

Hybrid combines:

Predictive + Agile.

Very common.

Especially in enterprise technology.

-----

===== Hybrid Example =====

Cloud migration.

Predictive:

  * budget approval
  * compliance milestones
  * security governance

Agile:

  * feature migration
  * testing
  * rollout iterations

Same project.

Mixed methods.

Hybrid reflects reality.

-----

===== Choosing the Right Approach =====

PMP encourages:

> Tailoring

Selection depends on context.

Questions:

===== Requirement Stability =====

Stable?

Predictive may fit.

Uncertain?

Agile may fit.

-----

===== Regulatory Pressure =====

Heavy compliance?

Predictive stronger.

-----

===== Need for Speed =====

Rapid learning?

Agile stronger.

-----

===== Stakeholder Involvement =====

Continuous engagement available?

Agile benefits.

Limited availability?

Predictive may help.

-----

===== Risk and Complexity =====

High uncertainty?

Adaptive approach often valuable.

Context determines method.

-----

===== Real-World Software Example =====

Example:

Your SSO integration work.

Predictive elements:

  * contract scope
  * client approval
  * launch deadline
  * security review

Agile elements:

  * API experimentation
  * incremental integration
  * technical refinement

This is often:

Hybrid.

Most software projects are.

Rarely pure waterfall or pure Agile.

-----

===== Predictive and Agile in PMP Exam =====

Modern PMP exam includes:

  * predictive
  * Agile
  * hybrid

Questions often ask:

What approach best fits scenario?

Correct answer depends on:

Context.

Not ideology.

PMP mindset favors:

Practical judgment.

-----

===== Common Misunderstandings =====

===== Mistake 1 — Agile Means No Planning =====

False.

Agile plans continuously.

Planning still exists.

Approach differs.

-----

===== Mistake 2 — Predictive Is Outdated =====

False.

Predictive remains valuable.

Especially:

  * infrastructure
  * compliance
  * construction
  * fixed-scope work

Many environments require it.

-----

===== Mistake 3 — Agile Is Faster =====

Not always.

Agile improves adaptability.

Speed depends on context.

Poor Agile can be slower.

-----

===== Mistake 4 — One Method Fits All =====

False.

PMP rejects dogma.

Tailoring matters.

Professional judgment matters.

-----

===== Why This Matters for PMP =====

Modern PM work spans:

  * predictive
  * Agile
  * hybrid

Strong PMs understand:

Methods are tools.

Not identities.

PMP emphasizes:

Selecting approach based on value and context.

This is mature project leadership.

-----

===== Software Engineering Perspective =====

Engineers frequently work in hybrid environments.

Examples:

Infrastructure:

Predictive.

Application feature work:

Agile.

Enterprise delivery:

Hybrid.

Understanding both approaches helps engineers:

  * communicate with business teams
  * plan realistically
  * reduce delivery friction
  * lead technical projects

Method awareness improves delivery capability.

-----

===== Key Takeaways =====

  * Predictive emphasizes planning and control.
  * Agile emphasizes adaptation and feedback.
  * Predictive suits stable requirements.
  * Agile suits uncertainty and learning.
  * Hybrid combines both approaches.
  * PMP values tailoring rather than ideology.
  * Context determines the best method.

-----

===== Reflection Questions =====

  * Which approach dominates my current work?
  * Where do I see predictive practices?
  * Where do I see Agile practices?
  * Could hybrid improve delivery in my projects?
  * Do I choose methods intentionally—or by habit?