Guidewire
MBR Project
Before the meeting
Reach out to your teams and bring their feedback to share.
The ninety minutes
8:00 to 9:30. Follow-ups logged against each topic.
ReferenceBamboo Project Management Office · Guidewire delivery tools
ReferenceBamboo · Guidewire Project Plan
01Why we are here
- Goals of this week
- Review and establish delivery process
- Prioritize business needs
02Delivery workflow and role assignment
- Name who receives the work at each hand-off. Two roles claiming one step is the gap
| Step | Owning role | Hands off to | |
|---|---|---|---|
| 1 | Request received and logged | ||
| 2 | Ticket opened and reviewed for completeness | ||
| 3 | Prioritized into a sprint | ||
| 4 | Elaboration and requirements written | ||
| 5 | Test design | ||
| 6 | Development | ||
| 7 | QA execution | ||
| 8 | UAT | ||
| 9 | Release approval | ||
| 10 | Deploy and production check |
DecisionOne owning role against every step, and the hand-off named at each boundary.
03PMO priority planning and shifting priorities
- Who sets the order today
- What a mid-sprint change costs: rework, carryover, retest, missed UAT
- Horse-trading process for critical priorities
- Where the ranked list gets published
ReferenceSprintkeep · Bamboo Maintenance Tracker
DecisionOne prioritization forum, one approver for mid-sprint changes, and the one-in-one-out rule that goes with it.
Additional topics
Discussed with the roles listed, as needed.
Intake and priority
Where requests come from and who ranks them.
Output: one intake path, one forum, one rule for mid-sprint changes.
Ticket quality
What a complete ticket contains before it enters the queue.
Output: required fields, and the rule for sending one back.
Elaboration and readiness
How current state and downstream impact get checked, and how long that should take. Being asked about above us. Verify impact to other platforms and tracks.
ReferenceTrackKeep · Bamboo Guidewire cross-track
Output: what ready for development means, who signs it, the cycle time we defend.
Test design, environments, data
When QA joins, and whether environments and data support the cases we write.
Output: the test design review, an environment owner, a refresh schedule.
Defect and regression reporting
Severity, sprint versus production defects, and tracing a bug to the case that missed it.
Output: severity scale, report format, who publishes it.
UAT and release
A realistic UAT window, what blocks a release, and deployment day.
Output: minimum UAT window, go/no-go rule, rollback path.
Estimation, retrospectives, metrics
Count bugs raised during delivery and regression issues per release, read release over release, to tell whether testing and development are improving or we are moving the same defects around.
Output: the measures, who reports them, the cadence.
Org chart, permissions, ESD process
Access rights that key off the org chart, and where production issues escalate after hours.
Output: org chart owner, review date, escalation matrix.
Proposed topics
Anything not already on the agenda. Add it before 8/22.
Click to choose a file, drag one here, or paste from the clipboard
Images are resized before saving. Do not include full policy numbers or customer names.