One vocabulary across three frameworks
Project management spans several methods — PMBOK, PRINCE2 and Agile — that often describe similar ideas with different words. This reference defines the core terms from each so you can read a plan, a status report or a sprint board and know exactly what is meant. Search by keyword or filter by framework to find the term you need.
How it works
Project terms cluster around three jobs: defining scope, tracking progress and controlling change.
Define scope → WBS / product breakdown structure, baseline, milestone
Track progress → critical path, earned value (SPI = EV/PV, CPI = EV/AC), velocity, burndown
Control change → tolerance, exception report, change request, risk register
Earned value links scope and progress numerically: an SPI below 1 means the project is behind schedule, and a CPI below 1 means it is over budget. PRINCE2 adds governance gates so a project board can stop or redirect work between stages.
Tips and notes
- A task on the critical path has zero float — protect those tasks first when resources are tight.
- SPI and CPI are ratios: 1.0 is on plan, above is good, below needs a recovery plan. They are most useful tracked as a trend, not a single snapshot.
- PRINCE2 tolerance defines how far a stage can drift before it must escalate — set it deliberately so the board isn’t flooded with exception reports.
- Agile velocity is a planning aid, not a productivity score; comparing teams by velocity is meaningless because story points are relative to each team.