ACP Corporate case studies
ACP Corporate · Put your knowledge to work in context.
ACP Corporate is an agile certification aimed at practitioners who apply agile thinking inside established organisations rather than in greenfield product teams. It suits project and programme managers, delivery leads, business analysts, PMO staff and change managers who must reconcile iterative delivery with fixed budgets, audit trails, procurement rules and layered approval chains. The ACP Corporate case studies are 5 cases and about 3,729 words.
1The Utilisation Metric That Ate the Retrospective
A payments company is nine months into an agile adoption covering eleven squads. The Enterprise Delivery Office still measures every squad against an 85% utilisation target, and individual performance ratings are calculated from the number of story points each person completes.
769 words, about 4 min2The Sponsor's Pet Epic and the Compliance Mandate
A life insurer runs six squads on an annual funding cycle. The product owner has 260 story points of capacity across six squads for the next two sprints and three candidate epics: Epic A - regulatory reporting change.
770 words, about 4 min3The Director Who Heard It Last
A European retail bank is seven months into an enterprise agile programme with seven teams. The Operations Director - who owns 900 contact-centre staff and 40 branch operations managers who will actually use the new onboarding service - discovered a material change to the customer onboarding flow two days before a release, when a branch manager forwarded her the internal release note.
702 words, about 4 min4Forecasting a Statutory Date with a Borrowed Specialist
A government digital service team has a statutory go-live date 14 weeks away and works in two-week sprints, leaving seven sprints including the current one. The remaining backlog is estimated at 240 story points; throughput for the last six sprints was 32, 41, 28, 37, 22 and 35 points.
722 words, about 4 min5The Audit Finding That Reads Like a Waterfall
An internal audit of a general insurer's claims platform found three things: the calculation change released in March had no documented traceability from requirement to test; release notes were missing for two of the last nine production releases; and one release had no recorded approval. Audit has rated the finding "major" and recommends that the teams must produce a full requirements specification and obtain formal change approval before every release.
766 words, about 4 min