In complex projects the most common mistake is not choosing the wrong tool, but choosing it too early. Context must be read first, the value to be delivered defined second, and only then should a technique be selected. This article summarises a technical analysis comparing PMBOK® 6, 7 and 8 with AACE International Recommended Practices (RP) around three adaptive capabilities.
Download the full white paper (PDF, 6 pages): English version · versión en español.
Taleb (2007) frames it through his distinction between Mediocristan and Extremistan: managers who act as if everything were predictable are exposed to black swans, improbable events that break the established order. Managers who accept uncertainty design their controls to absorb it.
1. Read uncertainty
The first adaptive capability is acknowledging what we do not know. CPM, developed at DuPont in the late 1950s, assigns a single duration per activity and does not model risk. PERT, developed for the U.S. Navy Polaris program, uses three estimates per activity and turns the schedule into a probability distribution:
More than a mathematical refinement, it is a change of stance: the project stops being a certain plan and becomes a range of scenarios.
AACE perspective. RP 57R-09 recommends Monte Carlo simulation on the complete CPM model. Where several paths converge on a single milestone, the successor is riskier than any of the merging paths (merge bias), an effect classic PERT ignores and that leads it to underestimate total duration.
2. Adjust time without losing direction
The critical path, calculated through the forward and backward passes, identifies the activities with zero total float (RP 49R-06): this is where the schedule lever sits. Two compression techniques act on it:
- Crashing: add resources to critical activities. Shortens duration at the cost of higher spend and diminishing returns.
- Fast tracking: overlap activities originally planned in sequence. Saves time at the cost of rework and integration risk.
Their role changes across editions: in PMBOK 6 they are deterministic tools of the schedule process; in PMBOK 7 they are integrated into the planning and delivery domains; in PMBOK 8 they become a dynamic governance mechanism fed by actual performance data.
AACE perspective. Compression can turn a near-critical path into a critical one, so near-critical paths must be monitored too (RP 92R-17). Every acceleration should be documented and analysed (RP 52R-06 and 29R-03), because in engineering and construction it often ends in a contractual dispute.
3. Sustain value over time
The central tool is the monitoring plan, provided it is robust (objective measurement, formal documentation, traceability) and versatile (able to revise its own indicators). Indicators are designed during planning, not at the end, and adjusted in action.
The hybrid PMBOK 8 approach keeps the structural metrics of the sixth edition (earned value, S-curves, variances) and integrates them with the value metrics of the seventh. AACE supplies the operational rigour through earned value consistent with EIA-748-C (RP 82R-13), variance analysis (RP 86R-14) and estimate at completion (RP 80R-13). For a refresher on SPI, CPI and EAC, see our guide to EVM for planners.
PMBOK and AACE: complementary, not competing
| Capability | PMBOK 6 / 7 / 8 | AACE (RP) | What AACE adds |
|---|---|---|---|
| Reading uncertainty | PERT, three-point estimates | 57R-09 · 40R-08 | Monte Carlo on the full network; avoids merge bias |
| Critical path | Forward and backward passes, zero float | 49R-06 · 92R-17 | Monitor near-critical paths as well |
| Compression | Crashing and fast tracking | 91R-16 · 52R-06 · 29R-03 | Document and justify every acceleration |
| Baseline | Baseline (v6), adaptation (v7) | 27R-03 · 37R-06 · 38R-06 | Declare schedule maturity (Class 5 to 1) |
| Performance | EVM (v6), value (v7), hybrid (v8) | 82R-13 · 86R-14 · 80R-13 | Move from variance to forecast |
In short, PMBOK 7 and 8 provide the why of adaptation (value), while AACE provides the how, backed by evidence.
An open question for the community: if schedule compression becomes a continuous, data-driven governance decision, which indicator should trigger it in your projects: schedule variance, or the value lost for every week of delay?
PMBOK® is a registered mark of the Project Management Institute, Inc. AACE® is a registered mark of AACE International. This article is an independent technical analysis.