PRINCE2 Agile combines the governance and control of PRINCE2 with agile delivery approaches. Central to effective governance is the concept of tolerances. Tolerances define the permissible variation in project parameters before formal escalation is required. Clear tolerances give teams authority to adapt day-to-day work while preserving the project board’s strategic control.
What tolerances are and why they matter
A tolerance is a boundary around a target for a controllable element such as time, cost or scope. If the element remains inside that boundary, the project can continue without invoking exception procedures. When a tolerance is forecast to be exceeded or is exceeded, the project manager must notify the project board and seek a decision.
In PRINCE2 Agile, tolerances are important because agile teams need freedom to adjust how work is delivered while the board still needs assurance that the project will meet its objectives. Well-defined tolerances avoid unnecessary interruptions and ensure that escalation happens only when a decision at board level is required.
Typical types of tolerances
Common tolerances used in PRINCE2 and adapted for agile contexts include:
• Time: allowed variation in schedule at project, stage or iteration level. In agile teams this can be expressed as permitted delay in milestones or release dates.
• Cost: acceptable deviation in the budget or forecasted expenditure.
• Scope: permitted change in functionality or requirements; in agile this often maps to which backlog items can be deferred or reduced.
• Quality: acceptable variance against quality criteria or acceptance standards.
• Risk: tolerance for exposure to risk, often expressed as the level of residual risk the board will accept.
• Benefits: acceptable deviation in expected benefits or benefit realisation timeframes.
These tolerances apply at different levels. The project board sets project-level tolerances. Project managers translate those into stage-level and team-level tolerances. Agile teams then operate within the delegated limits.
Applying tolerances in an agile delivery
Agile delivery practices and PRINCE2 governance can complement each other when tolerances are used thoughtfully.
• Define tolerances for the life of the project and review them at control points. For example, the board may set a project-level time tolerance of plus 10 percent on the planned delivery date and delegate smaller tolerances to stage managers.
• Use timeboxing to control time tolerances. Fixed-length iterations or sprints help keep delivery predictable. If a sprint forecast breaches a tolerance, the issue is raised rather than continuing silently.
• Treat scope as the flexible parameter where appropriate. In many PRINCE2 Agile scenarios the board may choose to fix time and cost while allowing scope to flex, managed via prioritisation of the product backlog. This should be made explicit so teams know what can change and what cannot.
• Make quality non-negotiable where required. If quality tolerance is tight, teams must not sacrifice acceptance criteria to meet time or cost targets.
Practical tips for setting tolerances
• Keep tolerances simple and measurable. Use percentages, absolute units of time or money, or clear acceptance criteria so it is obvious when a tolerance is nearing its limit.
• Align tolerances with decision points. Tolerances should support governance controls such as end-of-stage assessments and major release reviews.
• Communicate delegated authority. Everyone should know which decisions the team can make without escalation and which require board approval.
• Use visual controls and forecasts. Regular burn charts, forecasts and highlight reports help detect tolerance drift early.
• Revisit tolerances as the project evolves. Early assumptions may change and tolerances that were sensible at project start might need adjusting.
Managing breaches and exceptions
When a tolerance is forecast to be exceeded the project manager should follow the PRINCE2 exception process. That normally involves creating an exception report and recommending corrective options for the board. In agile settings the report may include alternative scope compositions, re-phasing of releases, or revised acceptance criteria. The key is that breaches trigger a governance conversation, not panic-driven adjustments within the team.
Final thoughts
Tolerances are the mechanism that makes controlled agility possible. They provide teams with the freedom to manage delivery while ensuring the project board retains oversight of outcomes that matter. By setting clear, measurable tolerances and aligning them with agile practices like timeboxing and backlog prioritisation, organisations can maintain control without undermining the responsiveness of delivery teams.
For formal training and practical courses on applying these ideas in real projects, Find courses at Knowledge Train.
Top comments (0)