Manage by Stages is a core PRINCE2 principle that divides a project into distinct management stages, providing control points where the Project Board reviews progress and decides whether to continue. In PRINCE2 Agile, this principle is enhanced by aligning management stages with agile concepts like…Manage by Stages is a core PRINCE2 principle that divides a project into distinct management stages, providing control points where the Project Board reviews progress and decides whether to continue. In PRINCE2 Agile, this principle is enhanced by aligning management stages with agile concepts like releases and timeboxes. A management stage is the period a Project Manager works under delegated authority before requiring Project Board approval to proceed. This creates natural governance and 'go/no-go' decision points, ensuring the project remains viable and aligned with the business case. In an agile context, a management stage often corresponds to a release, which is a deployable increment of the product delivered to users or the operational environment. Releases group together valuable features that provide business benefit, allowing frequent delivery of working products rather than one large delivery at the end. Within each management stage or release, work is organized into timeboxes. A timebox is a finite, fixed period of time during which work is completed and a defined outcome or deliverable is produced. Timeboxes are never extended; instead, the scope is flexed to meet the fixed deadline, reflecting the agile behavior of protecting the level of quality and time while allowing scope to vary. Sprints in Scrum are a common example of a low-level timebox. PRINCE2 Agile distinguishes between management stages (governance-focused, PRINCE2) and delivery-focused releases and timeboxes (agile). This layering allows senior management to retain control at stage boundaries while empowering delivery teams to work iteratively and incrementally within timeboxes. The behaviors underpinning this include transparency, collaboration, and self-organization. By combining Manage by Stages with releases and timeboxes, PRINCE2 Agile balances rigorous project governance with agile flexibility, enabling controlled yet adaptive delivery. This integration ensures continued business justification while promoting frequent, incremental value delivery to stakeholders throughout the project lifecycle effectively.
Manage by Stages with Releases and Timeboxes
Manage by Stages with Releases and Timeboxes is a key concept in PRINCE2 Agile that shows how the traditional PRINCE2 principle of Manage by Stages works together with agile delivery mechanisms such as releases and timeboxes. Understanding this integration is essential for the PRINCE2 Agile Foundation exam.
Why It Is Important In PRINCE2, a project is divided into management stages to give the Project Board control at key decision points. In agile environments, work is delivered incrementally through releases and short, fixed-length periods of work called timeboxes. Blending these approaches means you keep the governance and control of PRINCE2 while gaining the flexibility, frequent delivery, and responsiveness of agile. This combination allows senior management to retain oversight (through stage boundaries) while teams deliver value regularly (through timeboxes and releases).
What It Is Management Stages: These are the sections of the project that the Project Board manages, one at a time. Each stage ends with a decision point where the board decides whether to continue, using the Stage Boundary process.
Releases: A release is a transition of one or more products into operational use. Releases group together increments of the product and can happen within or across stages. Releases deliver usable, valuable outputs to the customer.
Timeboxes: A timebox is a fixed period of time in which work is completed. There are two types: • Low-level timebox (e.g., a sprint or iteration) - a short period, typically two to four weeks, in which a team produces working products. • High-level timebox - a longer period that may contain several low-level timeboxes and often aligns with a release or a management stage.
How It Works The relationship can be seen as a hierarchy of containment: • A management stage can contain one or more releases. • A release can contain one or more timeboxes. • Multiple low-level timeboxes can sit inside a high-level timebox.
A critical feature of a timebox is that its time is fixed - the deadline does not move. Instead, scope is flexed using prioritisation techniques such as MoSCoW (Must have, Should have, Could have, Won't have this time). This ensures the most valuable features are always delivered first, and lower-priority items may be dropped if time runs short.
Stage boundaries provide the formal PRINCE2 control points where the Project Board reviews progress, checks the business case, and authorises the next stage. Within those stages, teams work in timeboxes and produce releases, delivering value frequently without needing constant board intervention.
Key Points to Remember • Time and cost are fixed; scope and quality are variable (but quality criteria are not compromised - lower priority features are dropped instead). • Timeboxes are never extended - you do not add time. • Releases deliver value to the customer and may occur at various points during the project. • Stages give the Project Board control; timeboxes give teams a rhythm for delivery.
How to Answer Questions in the Exam Exam questions may test your understanding of the difference between stages, releases, and timeboxes, or how they fit together. Read the question carefully to identify which level is being described. If a question describes a fixed period where scope is prioritised and flexed, it is referring to a timebox. If it describes a decision point for the Project Board, it is a stage boundary. If it describes delivering product into operational use, it is a release.
Exam Tips: Answering Questions on Manage by Stages with Releases and Timeboxes • Remember the containment order: stage > release > high-level timebox > low-level timebox. • When a question mentions a fixed deadline that cannot move, the answer almost always involves flexing scope, not extending time. • Associate MoSCoW prioritisation with timeboxes - it is the mechanism for flexing what gets delivered. • Do not confuse a release (delivering product into use) with a timebox (a fixed period of work). • Recall that governance and Project Board control come from management stages, while frequent delivery comes from timeboxes and releases. • Watch for distractor answers suggesting that time or quality criteria should be compromised - PRINCE2 Agile protects both by flexing lower-priority scope. • Keep answers simple and definition-focused; Foundation questions test recall and understanding rather than complex analysis.
