Agile does not mean unaccountable. This playbook explains Schneider's financial governance model in team-friendly language: why funding moved from annual projects to quarterly tranches against value streams, what an investment gate actually checks, how teams report spend and outcomes without a parallel bureaucracy, and what to do when the numbers say stop. Written for the people inside the process rather than the people who designed it, with a glossary that translates finance vocabulary (CapEx, benefits realisation, cost of delay) into the decisions a team faces day to day.
📊 For the PMO
The translation layer between your governance model and the teams living inside it. It sets expectations you rely on — spend and outcome reporting without parallel bureaucracy, tranche discipline, dignified stops — in language teams accept, which lowers the enforcement cost of every process you run. Recommend it to every newly funded team. Track this: teams whose spend reports arrive without chasing; that number measures whether the governance model is understood or merely imposed.
🎯 For Product Owners
Governance in the language of the decisions you actually face: why funding is quarterly tranches, what a gate checks, how to report spend without a parallel bureaucracy, and what happens when the numbers say stop. The glossary translating CapEx, benefits realisation and cost of delay into working terms is the part you will reopen. Takeaway for your backlog: order your next tranche's items by cost of delay and keep the calculation — it is the evidence your next gate wants.
🤝 For Scrum Masters
Read this to answer the question your team asks in every planning: why does funding work like this? The playbook explains tranches, gates and honest spend reporting in team language, so cadence pressure stops feeling arbitrary. It also tells the team what 'stop' means before it happens to an initiative they care about — better discussed in advance. Try this with your team: run the glossary as a fifteen-minute session; shared finance vocabulary removes a surprising amount of planning friction.
Topic
Format
Intended for
