ART readiness
Seven teams mapped to the value stream. RTE, PMs, SMs trained. Backlog refined, dependencies surfaced before planning.
Train launch
First PI planning event. Rockmere consultants embedded in the room. By the readout, the train owned its commitments.
Stabilization
System demos, IP iteration, inspect and adapt. PI Objective achievement reached 73% by end of PI 2.
Predictability
Cadence locked. PI Objective achievement at 87%. RTE owned the train. Rockmere exited to quarterly advisory.
The challenge
A Tier-2 P&C insurance carrier launched a 9-team SAFe® Agile Release Train in 16 weeks and reached 87% PI Objective achievement by PI 3, after two prior SAFe® attempts had rolled back. The difference was sequencing: we fixed portfolio-level funding flow before re-launching the train, so the failure mode that killed the first two attempts could not recur.
A Tier-2 P&C insurance carrier with $4.2B in annual premium had attempted SAFe® twice in the prior three years. The first attempt, led by a Big 4 firm, ran for 11 months before rolling back. The second, led by a different consulting firm that specialised in SAFe®, ran for 7 months before being quietly relabeled "Agile-at-scale" and continuing without the original framework discipline. By the time we walked in, the word "SAFe®" carried scar tissue across the IT and business organisations.
Both attempts failed the same way. Teams were trained. Release Trains were named. PI Planning events were held. PI Objectives were committed to. But funding decisions happened in a monthly steering committee that sat outside the SAFe® cadence. The teams couldn't commit to PI Objectives that hadn't been funded. Funding decisions kept moving target outcomes mid-PI. Trust between business and IT eroded. The practice collapsed.
The CIO was direct in the initial call: "We're not running this play a third time unless you can show me the structural difference. I have one more attempt in me before the board takes it off the table." This SAFe® ART launch case study describes how a 9-team Agile Release Train at this Tier-2 P&C carrier hit 87% PI Objective achievement by PI 3, and how the failure modes of the prior two SAFe® attempts were structurally prevented from recurring.
The constraints
The build sat inside an insurance carrier's regulatory and operational reality.
- NAIC Model Audit Rule and state DOI oversight. Every release had to produce audit evidence acceptable to the carrier's external auditor and to the state Departments of Insurance in each jurisdiction. PI Objectives, Definition of Done, and Iteration Review minutes all had to be admissible artefacts.
- SOX evidence at the program increment level. Internal audit needed quarterly attestation that the SAFe® cadence was being followed and that change control was traceable from feature to deployment.
- Trust deficit from two prior failures. Veterans of the prior two SAFe® attempts were sceptical by default. Any new ceremony, role, or artefact had to earn its place against memories of the last two rollouts. We could not assume goodwill on the framework itself.
- CFO's office outside the cadence. Funding decisions historically moved on a monthly steering committee schedule that ignored the SAFe® calendar. Without realigning this, the ART would relive the prior failure modes.
- 9 teams, 84 people, 4 sites, 3 time zones. PI Planning logistics were non-trivial. A purely co-located model was not affordable; a purely distributed model had failed at the second attempt. We needed a hybrid model that would still earn the social bandwidth of a real PI Planning room.
Our approach
Tier-2 P&C carrier · SAFe® ART launched in 14 weeks
Start at Portfolio SAFe®, not Essential. Our diagnostic confirmed the binding constraint was portfolio-level funding flow, not team-level practice. We declined to launch ARTs in week one. The first six weeks were Lean Portfolio Management: Strategic Themes, Lean Budgets, Portfolio Kanban, and a monthly portfolio cadence that aligned funding decisions with PI cadence. Both prior firms had skipped this. The CFO's office had to be in the room for the first three of those weeks, which initially they resisted. The CIO made the call that they had to attend. By week six, the CFO's deputy was the one running the Portfolio Kanban review.
Be honest about which value streams should be ARTs. The client's original scope called for three ARTs: claims, billing/payments, and new business. We profiled all three. Only claims had the team count (9 teams), the business sponsorship (a committed EVP), and the outcome clarity (defined business metrics owned by the sponsor) to sustain an ART. Billing/payments had the team count but not the sponsorship. New business had the sponsorship but only 4 teams. We launched one ART on claims and parked the other two for subsequent launches under internal SPCs. The CIO later told us this was the moment he decided we were different.
Co-train internal SPCs from week one. The client had four internal practitioners at SPC-candidate level: people who had done SAFe® coaching elsewhere or held lower SAFe® certifications and were senior enough to do the work. Our SPCT delivered the Implementing SAFe® certification course in week 4 and then mentored the four through co-facilitation of the ART launch. By engagement end, two certified as SPCs. The other two certified within three months. The credential authority that lets us deliver Implementing SAFe® inside an engagement (not just refer to a public class) is detailed on our credentials page.
Map every SAFe® artifact to an audit evidence requirement. Insurance is heavily audited. PI Objectives became quarterly attestations. Definition of Done included the SOX evidence requirements. Iteration reviews included compliance signoff. The audit team became an early sponsor rather than a late blocker. The NAIC Model Audit Rule and state DOI evidence trail mapped one-for-one to existing SAFe® artefacts, with no parallel paperwork stream. Same pattern we'd run successfully in financial services engagements, including the one detailed in our bank fraud investigation copilot case study.
What we delivered
The engagement delivered four things the carrier still runs today. First, a launched 9-team Agile Release Train on the claims value stream, with RTE, Product Management, and System Architect roles staffed and trained. Second, a Lean Portfolio Management operating model with Strategic Themes, Lean Budgets, Portfolio Kanban, and a monthly portfolio cadence. Third, internal capability: four internal SPCs at engagement end or shortly after, capable of launching subsequent ARTs without external support.
Fourth, the audit-evidence integration pattern: SAFe® artifacts mapped to the client's audit framework, with the audit team participating as a SAFe® stakeholder. The named lead from internal audit attended every Inspect-and-Adapt event for the first three PIs and reviewed the artefact mapping at each one.
The operational tooling was configured to match, not bolted on afterward. Jira Align workflows reflected the carrier's value stream. Confluence templates covered PI Objectives, features, and Inspect-and-Adapt minutes. A Miro PI Planning room template the carrier still uses for every quarterly event rounded out the handoff.
The result
PI Objective achievement climbed from 64% in PI 1 to 87% by PI 3, while average idea-to-production time fell from 7.4 months to 2.9. The train improved on every tracked measure across three program increments.
| Metric | Baseline (pre-launch) | PI 1 | PI 2 | PI 3 |
|---|---|---|---|---|
| PI Objective achievement | n/a | 64% | 78% | 87% |
| Time from idea to production (avg) | 7.4 months | 5.1 | 3.8 | 2.9 months |
| Deployment frequency (per team per quarter) | 1.4 | 3.1 | 4.6 | 6.2 |
| Cross-team dependencies surfaced at PI Planning | n/a | 47 | 38 | 24 |
| Internal SPCs certified | 0 | 2 | 4 | 4 |
By PI 3 (roughly 9 months after engagement start), the client launched a second ART on the new-business value stream. Led by the internal SPCs without Rockmere involvement. That ART hit 71% PI Objective achievement in its PI 1, comparable to what most external-led launches achieve. The CFO's deputy presented the working-capital impact of the cycle-time reduction to the carrier's board in the same quarter.
Engagement timeline
| Week | Workstream |
|---|---|
| Weeks 1–2 | Diagnostic. Portfolio dysfunction analysis. Value stream profiling. Told the CIO in week 2 that two of his three proposed ARTs shouldn't launch yet. |
| Weeks 3–6 | Lean Portfolio Management install. Strategic Themes drafted with the EVP of claims. Lean Budgets workshop with the CFO's office (week 3 attendance was 60%; by week 6 it was 100%). |
| Weeks 4–5 | Implementing SAFe® class for the four internal SPC candidates. The class was taught on-site, which mattered: two of the candidates had to be pulled into ART preparation conversations during breaks. |
| Weeks 7–10 | ART preparation. RTE training. Team training. Program backlog preparation. The audit lead joined the prep sessions in week 8 and stayed through the engagement. |
| Weeks 11–12 | PI Planning event 1. Co-facilitated by the SPCT and two internal SPC candidates. 64% PI Objective achievement at PI close. |
| Weeks 13–16 | PI 1 execution support. Iteration coaching. Inspect-and-Adapt facilitation. First I&A surfaced the funding-cadence issue that had killed the prior attempts; this time the LPM fix was already in place to absorb it. |
| Months 5–10 (sustain) | Quarterly PI Planning support. Portfolio cadence coaching. Internal SPC mentorship. Second ART launch preparation, led by internal SPCs. |
What survived past our engagement
The Agile Release Train is in its 7th PI as of writing. The Lean Portfolio Management operating model is operational. The audit-evidence integration pattern has been adopted across the broader IT organisation. The four internal SPCs have launched a second ART and are preparing to launch a third.
Specifically, four artefacts now belong to the carrier.
- The Implementing SAFe® training cadence. Run internally by the lead SPC, with new candidates trained every other quarter. The carrier no longer pays for external SAFe® certification of its own staff.
- The Lean Portfolio Management operating model. Strategic Themes refreshed semi-annually with the executive team. Portfolio Kanban reviewed monthly with the CFO's office as a standing participant. Lean Budgets reset annually.
- The audit-evidence integration pattern. PI Objectives, Definition of Done, and Iteration Review minutes all flow into the carrier's GRC platform with no parallel paperwork stream. The internal audit lead attests quarterly that the SAFe® cadence satisfies SOX, NAIC Model Audit Rule, and state DOI requirements.
- A named owner with budget. The RTE for the claims ART owns the operating model. Portfolio governance sits with the CFO's deputy. The escalation tree is written and tested.
The carrier's CIO presented the SAFe® transformation at a regional insurance industry CIO summit. We supplied the presentation deck source data; the CIO did the speaking.
Where this fits
This is canonical SAFe® Consulting work in a regulated industry. The integration with audit and compliance is detailed in our Insurance industry page. The Lean Portfolio Management work is part of any enterprise-scale SAFe® engagement we run, and the agile coaching depth that backs the SPCT engagement is described under Agile Consulting.
The same regulatory-evidence integration pattern shows up in our bank fraud investigation copilot (SR 11-7) and in our Tier-1 automotive supplier OEE case study (IATF 16949). If you've had SAFe® attempts that rolled back, the issue is rarely team-level practice. It's almost always portfolio. Get in touch for a 30-minute diagnostic conversation about your prior attempt and what would need to change to make a relaunch work.