The bridge between a validated idea and a funded initiative. This deep dive explains what the investment board expects at each approval gate: the lean business case, the evidence pack from discovery and validation, the ask (people, budget, duration), and the outcome measures you commit to. You will see a real anonymised pitch that passed and one that was sent back, with the board's reasoning for both. Covers how the quarterly funding cadence works, what happens to initiatives that miss a gate, and how to right-size an ask for a first tranche.
📊 For the PMO
A calibration module for gate reviewers as much as for pitchers. It publishes what good looks like — evidence pack, lean business case, right-sized first tranche, committed outcome measures — and shows a pass and a send-back with reasoning, which anchors consistent board behaviour across quarters. Track this: send-back rates by reason; if one reason dominates, the guidance upstream of the gate needs fixing, not the teams.
🎯 For Product Owners
The most directly useful twenty minutes on the portal: what the board checks at each gate, how to size a first-tranche ask, and a real pitch that passed next to one that was sent back — with the board's reasoning. You are the person who writes and defends the case, so the anonymised examples are your calibration set. Takeaway for your backlog: draft your next ask as first-tranche only, with the outcome measures you would accept being held to.
🤝 For Scrum Masters
You will not present at a gate, but your team lives with what gets promised there. This module shows the funding cadence behind sprint pressure: tranche sizes, gate dates, and why a Product Owner suddenly needs capacity estimates. Understanding it makes you a better thinking partner before the pitch rather than a spectator after it. Try this with your team: review the next pitch's delivery assumptions together before submission, and flag the ones the team never agreed to.
Topic
Format
Intended for
