PRINCE2 Agile Practitioner case studies
PRINCE2 Agile Practitioner · Put your knowledge to work in context.
PRINCE2 Agile is a certification that blends the structured, governance-focused PRINCE2 project management method with agile ways of working. PeopleCert describes it as "a global best practice method that combines the structured, step-by-step approach of PRINCE2 Project Management with agile ways of working," aimed at helping practitioners balance agility with control. The PRINCE2 Agile Practitioner case studies are 5 cases and about 2,309 words.
1The 12-Week Fixed Deadline with a Scope-Shaped Hole
Meridian Housing, a mid-sized landlord, is running a PRINCE2 project to replace its tenant portal. The board has fixed an immovable go-live of 30 November because a regulatory reporting duty starts in December.
497 words, about 2 min2Daily Stand-up That Became a Status Meeting
On the Larkspur insurance claims project, the delivery team's daily stand-up is chaired by the team manager, Ken. It runs 35–40 minutes.
460 words, about 2 min3Tailoring the Business Case for a Two-Quarter Agile Delivery
Northgate Council is running a PRINCE2 Agile project to digitise blue-badge parking permits. The original business case was written as a single five-year benefits case with a break-even in year three.
455 words, about 2 min4AgileSHAPE When the Environment Is Hostile
Vantage Logistics is running a PRINCE2 Agile project to replace its warehouse management system. The AgileSHAPE-style assessment scored the environment badly on several axes: the customer is a single internal operations director who is unavailable for more than 30 minutes a fortnight; the team is split across three sites with a four-hour time-zone spread; the technology includes a 20-year-old integration layer with no documentation; and the organisation's governance requires a full change board for any scope adjustment.
454 words, about 2 min5Stage Boundary When the Sprint Went Badly
On the Halcyon payroll migration project, the second management stage contains four two-week sprints. Sprint 3 failed its sprint goal: the team committed to 40 story points and delivered 18, because an upstream data-quality issue was worse than expected.
443 words, about 2 min