Tools for running
Guidewire delivery.

Agents · anyone who hits a problem in Digital, PC or BC · titled “Something not working?” for agents

The intake form. Name, team, policy number, what you were trying to do, what the system did back, and a screenshot. Takes about half a minute.

Deliberately asks “could you finish?” rather than “what priority is this?” — the agent knows whether they were blocked, and that single answer sets how urgently it gets picked up. Nobody has to guess at a severity or work out whether something is a bug or intended behaviour before reporting it.

• Half a minute to file
• Paste or attach up to 10 screenshots
• Remembers your team
• No priority guessing

Project Management Office · support leads · whoever is on triage this week

Everything agents have filed, grouped so the same problem reported nine times reads as one issue with nine reports. Sort by what to work on first, mark what needs a Jira ticket, record the workaround, and see which issues are actually blocking people.

Turns a stream of individual complaints into a ranked list with volume behind it. An issue reported once by one agent and an issue reported nine times across two teams look completely different here — and that difference is what decides which one becomes a ticket first.

• Grouped by issue, not by report
• Open · needs ticket · ticketed · blocking
• Workarounds
• Volume and learning views
• Per-team filters

Project Management Office · BAs · delivery leads · anyone asking “where is my epic?”

The sprint and epic tracker for GWMAIN Track 1. Every maintenance epic, from BA elaboration through dev and QA to the release it shipped in, on one page you can filter, rank and export.

Replaces the spreadsheet that used to be rebuilt by hand every sprint. Because it reads the curated Master WIP set rather than raw Jira counts, it is the number the team can stand behind when someone asks what velocity is. The Blockers view reads the comment trail, so an epic sitting at “Ready for Dev” while approval landed three weeks ago stops hiding.

• Master WIP
• Velocity & Intake
• Blockers, from Jira comments
• Production Defects
• BA Sprint Planner
• Release Schedule, synced to Confluence
• Backlog Flow
• Drag-to-rank
• Export to Excel

Steering group · product owners · workstream leads

The nine MBR initiatives — Return Premium, Renewals, Billing Statements, Addresses, Commissions and the rest — each with the tickets actually in its scope, what the work is in plain language, who is blocked, and a burn-down of what is left. Tickets arrive by their MBR-0n Jira label, so nobody maintains a list by hand.

Answers what a steering meeting really asks: is this initiative moving, and what is in the way — without anyone decoding a Jira title like “GD INT: Revise verbiage”. It also proposes requirements nobody has written down yet, so gaps surface before a release rather than after it.

• MBR-01 to MBR-09
• Label-driven ticket mapping
• Plain-language ticket notes
• Suggested requirement gaps
• Blockers and owners
• Daily burn-down

Track leads · release managers · anyone sequencing work

Every initiative with an active or upcoming sprint, laid out on one timeline by planning start and deployment date. Hatched bars are still in requirements, solid bars are in build — and anything touching the same Guidewire system as another track is flagged.

Two tracks changing PolicyCenter in the same window is how a clean release turns into a regression hunt. This is the collision check nobody was doing, and it happens while the work is still being planned rather than when QA finds it.

• Cross-track collision flags
• Requirements vs build, at a glance
• Planning start → deployment
• Per-initiative detail

Project Management Office · portfolio planning · anyone answering “can we fit it?”

The FY26 and FY27 roadmap. Live hours logged from Jira worklogs by Guidewire tech and role, planned demand from the sizing spreadsheet, the variance between them, and a capacity heatmap showing which months are already oversubscribed.

Planning used to be a spreadsheet arguing with reality. This puts actuals and estimates on the same axis, so a T-shirt size can be checked against what similar work really cost — and a month at 120% utilisation shows up red before anyone commits to a launch date.

• Actuals vs planned demand
• Live Jira worklog burn
• FY27 planning grid
• T-shirt sizing reference
• Capacity heatmap
• Gantt view

Everyone on the Monday call · 11:00 PT

The weekly agenda, built from live data rather than retyped. MBR workstream ownership, new programs and their risk, D2C phases, special projects, renewal retention cohorts, and every epic and defect in the next two releases. Minutes and action items are captured in the same page, and each week archives itself.

The agenda used to be a deck someone rebuilt every Sunday. Now it reads the same sources the delivery tools do, so what is discussed on the call and what is in Jira cannot drift apart — and last week's version is one click away when somebody asks what was agreed.

• Live release contents
• Workstream ownership
• Retention cohorts
• Minutes and action items
• Weekly archive
• Print to PDF

MBR-04 · BAs and devs working the address change

A worked model of how an address moves through the Bamboo systems — where it is entered, where it is validated, and every downstream place it has to agree with itself.

Addresses touch PolicyCenter, BillingCenter, Digital and the documents that go out the door, which is why MBR-04 exists. Having one agreed picture of the workflow means requirements get written against the same model rather than against whichever part of it each person happens to know.

Anyone who needs to know who covers what

Who sits on which track, in which role, across maintenance, production defects, integrations and the other Guidewire workstreams.

The roster is what Sprintkeep checks a BA name against. When somebody starts doing BA work and nobody adds them here, their work shows up as “off-roster” in the velocity tables — so keeping this current is a reporting fix, not just a contact list.

• Track 1 · 2 · 3
• BA, dev, QA and PO coverage
• Feeds Sprintkeep's BA roster