Capstone: from mandate to authorized project, with exam strategy

This capstone runs the three early processes end to end on a second case, Harbor City Libraries, the invented public library system from PRIN-130 and PRIN-131. PRIN-130 built its business case, team and plans; PRIN-131 controlled its pilot branch stage. Here we go back to the start and follow the library from the mandate, through starting up, the decision to initiate, initiation and the decision to authorize the project. The lesson ends with exam strategy for questions on these processes. All figures are illustrative.

The mandate

The library board, Harbor City's governing body for its libraries, minutes the following: staff spend too much time on routine checkouts and returns, and room bookings are error-prone; the chief librarian is asked to bring forward a proposal for self-service and online booking across the six branches within three months; total spending must not exceed 1.2 million. This is the project mandate. It names a likely executive (the chief librarian), states the problem, gives a deadline for a decision and sets a cost ceiling, which becomes a project tolerance. It also hints at a solution (self-service), which starting up should examine rather than accept blindly.

Starting up

The library board appoints the chief librarian as executive, and she appoints the library's project lead as project manager. Previous lessons come from the city's earlier customer portal project, which left accessibility testing to the end and lost six weeks, and from a neighboring library system's self-service rollout, which found that uptake depended heavily on staff encouraging patrons in the first month. The project management team is designed: the manager of branch services as senior user; the city IT manager and, once contracted, the RFID kiosk vendor's delivery manager as senior suppliers; a city internal audit analyst and an uninvolved branch manager as assurance; the library's administrative officer as project support.

The outline business case compares do nothing, online booking only, and booking plus self-service. The self-service option costs about 900 thousand in year 0 and 200 thousand in year 1, freeing staff time and shortening queues, but its value depends on patron uptake. The project approach is to buy proven products, pilot one branch, then roll out in two groups, with accessibility testing built into each product's quality criteria from the start. The project brief assembles these, with the library board's tolerances, and the initiation stage plan proposes about six weeks of initiation.

Directing: authorize initiation

The board reviews the project brief and initiation stage plan at the end of week 2 and meets in week 3. It confirms that the outline business case suggests the project is worthwhile but highlights uptake as the key uncertainty; that the team is complete except the kiosk vendor, which the city IT manager covers for now; that the approach applies previous lessons; and that six weeks of initiation is proportionate. It authorizes initiation with tolerances of ±10 % on a small initiation budget and +2 weeks, and the executive informs the library board and branch managers.

Initiating

During initiation the project manager agrees tailoring (one PID with approaches as short sections; registers in a shared workbook; fortnightly highlight reports), prepares the management approaches, sets up controls, creates the project plan and refines the business case. The digital and data approach covers patron borrowing data and booking records, which are personal information. The commercial approach covers the kiosk procurement. The benefits management approach defines how staff hours, booking errors and queue times will be measured, with the pilot designed to measure uptake before rollout.

Because patron records are personal information, Harbor City Libraries' digital and data approach must reflect state law protecting library records, which most states have, and the library's privacy policy, and its accessibility criteria reflect the ADA, including the Department of Justice web accessibility rule for state and local governments.

Checking the whole package

The code below brings together several of the checks from this course and applies them to Harbor City Libraries: whether the early processes fit within the three-month deadline, whether the stage budgets stay within the library board's ceiling, whether stage tolerances nest within the remaining headroom, and whether every acceptance criterion has a quality method.

deadline_weeks = 13
timeline = [("Starting up", 2), ("Board: authorize initiation", 1), ("Initiation stage", 6), ("Board: authorize project", 1)]
elapsed = sum(w for _, w in timeline)
print(f"Mandate to authorized project: {elapsed} weeks (deadline {deadline_weeks}) ->", "ok" if elapsed <= deadline_weeks else "late")
ceiling = 1200
stages = {"Initiation": (30, 0.10), "Pilot": (360, 0.05), "Group A": (370, 0.05), "Group B": (340, 0.05)}
budget = sum(b for b, _ in stages.values())
headroom = ceiling - budget
stage_tol = sum(b * t for b, t in stages.values())
print(f"Planned cost {budget} thousand; ceiling {ceiling}; project headroom {headroom} thousand ({headroom / budget:.1%})")
print(f"Stage tolerances total {stage_tol:.1f}; reserve left {headroom - stage_tol:.1f} thousand ->", "ok" if stage_tol <= headroom else "do not nest")
criteria = {"Kiosk usable by wheelchair users": "accessibility audit", "Booking double-bookings under 2 a month": "pilot data review",
            "Checkout under 30 seconds for 90 % of patrons": "timed observation", "Staff time freed measured": None}
missing = [c for c, m in criteria.items() if not m]
print("Criteria without a quality method:", missing if missing else "none")

Mandate to authorized project: 10 weeks (deadline 13) -> ok
Planned cost 1100 thousand; ceiling 1200; project headroom 100 thousand (9.1%)
Stage tolerances total 56.5; reserve left 43.5 thousand -> ok
Criteria without a quality method: ['Staff time freed measured']

The early processes take ten weeks, within the three-month deadline. The planned cost of 1,100 thousand leaves 100 thousand of headroom under the library board's ceiling, about 9 %, and the stage tolerances use 56.5 thousand of it, leaving a reserve of 43.5 thousand. One acceptance criterion, measuring staff time freed, has no method; it is really a benefit measure rather than an acceptance criterion, so it belongs in the benefits management approach, with a time-sampling study before and after the pilot. The project manager moves it there and assembles the PID.

Directing: authorize the project

In week 10 the board reviews the PID and the pilot branch stage plan prepared at the stage boundary. It checks that the detailed business case still justifies the project, noting that the case depends on uptake and that the pilot stage is designed to measure it; that the project plan fits within the library board's ceiling with a reserve; that the approaches are consistent; and that the benefits approach will show whether staff time is actually freed. It authorizes the project and the pilot branch stage, with the tolerances above, and the executive reports the decision to the library board within the three-month deadline.

Exam strategy for the early processes

PRIN-120 described the exam formats used in recent years; check the current details with PeopleCert before booking. The Foundation exam was described as 60 multiple-choice questions in 60 minutes, closed book, with a pass mark of 36. The Practitioner exam was described as 70 questions in 150 minutes, open book with the official manual only, with a pass mark of 60 %. Foundation questions on these processes test definitions, purposes, sequence and roles. Practitioner questions place you in a scenario and ask what the right action, product or decision is at a particular moment.

Three traps recur. The first is confusing the project brief with the PID: if a question mentions the outline business case or the initiation stage plan, you are in starting up; if it mentions management approaches, the project plan or the detailed business case, you are in initiation. The second is confusing ownership with drafting: the executive owns the business case even if the project manager writes it. The third is overdoing it: an answer that adds more documents, more meetings or more approvals is not automatically better. PRINCE2 favors the option that achieves the purpose proportionately.

Using the manual in the Practitioner exam

In an open-book exam, the manual is a reference, not a textbook. Before the exam, learn where the process chapters are, where each process's activities and their inputs and outputs are listed, where the management product outlines are, and where the role descriptions sit. Mark them with tabs if the rules allow. During the exam, use the manual to confirm a detail you are unsure of, such as which product is an output of a particular activity, rather than to learn a topic for the first time. If a question can be answered by reasoning from purpose and roles, answer it and move on.