Portfolio Planner · GW Main Roadmap · Project Management Office
Roadmap Planner
By Track
⚠ Needs Attention
🚀 Launched & Launching Soon
FY26 · Sep 2025 → Aug 2026
Actuals vs Estimates
Live data from JIRA worklogs by GW Tech (PC/DIG/BC/INT) × Role (BA/DEV/QA). Toggle the grouping below to see variance by track, by guidewire team, or by role.
Loading…
JIRA · bambooinsurance.atlassian.net LIVE
JQL:
project in (GWMAIN, GWPRO, GWINIT, SPEC, CLA) AND issuetype = Epic AND (resolved is EMPTY OR resolved >= "2025-09-01")📊 Live JIRA Project Burn · FY26
Hours logged · by track × fiscal month click a track to drill into projects
·
Methodology: Hours come from JIRA worklogs (subtask-inclusive) bucketed to each worklog's real
started date.
Months Sep'25–May'26 are actuals. Months Jun'26–Dec'26 are projections based on the average of the last 3 months of actuals.
The BAU multiplier scales the spreadsheet's planned demand (which models only roadmap initiatives) to estimate total operational demand including maintenance and BAU work.
Source: roadmap_project_actuals · synced via Cloudflare Worker.
⚖️ Live Actuals vs Planned Demand · Variance
Plan vs Actual · monthly variance with BAU adjustment
JIRA actuals vs spreadsheet demand (raw + BAU-scaled)
📋 Initiative Planning Estimates · Spreadsheet-derived
Initiative breakdown
Within ±5%
5–15%
>15% over
FY2027 · 12 month horizon
2027 Planning Grid
Enter initiatives with target launch and requirements start dates. BA/DEV/QA hours pull automatically from Project Resources (12-month FY2027 totals); rank and strategic benefit are set here.
2027 Initiative plan · grouped by track
| Rank | Initiative | Track | Type | Owner | Requirements Start | Target Launch | BA hrs | SA hrs | DEV hrs | QA hrs | Total | Strategic Benefit $ | Notes | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Portfolio Totals | 0 | 0 | 0 | 0 | 0 | — | ||||||||
Resource Model · Nov 2026 → Feb 2028
Project Resources
Hours by track, platform, and t-shirt size. Pick a size per platform & role —
the avg hours are a monthly rate, pulled live from the Sizing Sheet, applied to
every month in the row's start + duration window (or all months if undated).
📊 Monthly Rollup · Capacity vs Scope
Scope computed live from the initiative grid below · capacity from the Team assignments on the 2027 Heatmap
🧩 Initiative Resource Grid · by track
Estimation Model · avg hours per role
Sizing Sheet
T-shirt size hour models per platform. Edit any cell — changes apply immediately
when you pick a size in the 2027 Planning Grid.
STANDARD SIZING · TRACKS 1, 3, 4 & DATA WAREHOUSE
From your Sizing sheet · BA / DEV / QA / UX avg hours · used when you pick a size in the grid
| Platform | Size | BA hrs | DEV hrs | QA hrs | UX hrs | Total |
|---|
NEW PROGRAMS SIZING · TRACK 2 (GWPRO) & TRACK 5 (WILDFIRE) ONLY
New Programs hour model · size scale XS → L · applied automatically when sizing Track 2 and Track 5 initiatives in the Planning Grid
| Platform | Size | BA hrs | DEV hrs | QA hrs | UX hrs | Total |
|---|
Resource Roster · source of truth: Confluence “2026 Scrum Teams” · synced Jul 14, 2026
Team roster
Everyone on the GW Tech program — edit any cell, add or remove people, and the
rollup updates live. Deactivating or removing someone also pulls their FTE out of
capacity in Project Resources, the 2027 Heatmap, and the planning footer.
RESOURCE ALLOCATION ROLLUP
FULL ROSTER · EDITABLE
Gantt View · monthly · FY2026 actuals window
2026 timeline
Gantt View · monthly · Jan 2027 → Mar 2028
2027 timeline
Demand vs Capacity · monthly · by team & role · FY2026
2026 heatmap
Read the colours: green = headroom, yellow = healthy, red = oversubscribed. Hover any cell for the exact gap.
FY2026 utilization · 16-month view
< 70%
70–85%
85–100%
100–120%
> 120% red flag
Monthly capacity snapshot
capacity − demand = gap · hours
Demand vs Capacity · monthly · by platform & role · Nov 2026 → Feb 2028
2027 heatmap
People assigned per track × platform × role (from the Team tab), rolled up into the combined view at top.
Demand comes live from Project Resources. Green = headroom, red = oversubscribed or unstaffed. Hover cells for detail.
FY2027 assignment & utilization · by track · platform · role
< 70%
70–85%
85–100%
100–120%
> 120% red flag