Vact Project Governance: Decision Structures That Enable Speed
Project governance defines how decisions are made, who has authority over what, and how the project is monitored and controlled. Good governance enables speed by clarifying who can make which decisions. Bad governance creates bottlenecks by requiring unnecessary approvals and adding bureaucratic overhead. The goal is the minimum governance necessary to maintain alignment, manage risk, and ensure accountability.
Project Governance: Decision Structures That Enable Speed
Governance Layers
Steering Committee
A small group (3-5 people) of senior stakeholders who provide strategic direction, approve major scope changes, and resolve escalated issues. The steering committee typically includes the executive sponsor, the senior user representative, and the senior technical representative, similar to PRINCE2’s Project Board.
The steering committee meets monthly or at major milestones. They receive status reports and make decisions on issues that exceed the project manager’s authority.
Project Manager Authority
Define what the PM can decide without escalation:
| Decision Type | PM Authority | Requires Escalation |
|---|---|---|
| Daily task assignment | Yes | No |
| Sprint scope adjustments | Yes | No |
| Technical approach | Yes (with tech lead) | No |
| Budget variance < 10% | Yes | No |
| Scope change < 1 week effort | Yes | No |
| Budget variance > 10% | No | Yes (steering committee) |
| Timeline change > 2 weeks | No | Yes (steering committee) |
| Scope change > 2 weeks effort | No | Yes (steering committee) |
Team Authority
Define what the team can decide without PM involvement. Agile teams should have authority over technical implementation decisions, sprint task breakdown, and code-level design choices.
Governance in Agile Projects
Agile governance is lighter than traditional project governance but not absent. Key mechanisms include:
Sprint reviews serve as regular governance checkpoints where stakeholders inspect the increment and provide direction.
Product Owner authority over backlog priority provides continuous scope governance without a change control board.
Retrospectives provide process governance through team self-inspection and adaptation.
Definition of Done provides quality governance by establishing minimum standards for completed work.
Designing Governance for Your Project
Match Governance to Risk
| Project Risk | Governance Level | Checkpoints |
|---|---|---|
| Low (small, internal, familiar) | Light | Monthly review, sprint demos |
| Medium (moderate budget, some uncertainty) | Standard | Biweekly steering, sprint demos |
| High (large budget, new technology, external) | Rigorous | Weekly steering, phase gates |
Governance Anti-Patterns
Too many approvers. Every additional approver adds delay. Limit approval authority to the fewest people possible. Use RACI to clarify who approves versus who is consulted or informed.
Governance as control. Governance exists to enable good decisions, not to create oversight for its own sake. If a governance mechanism does not improve decision quality, it is overhead.
Missing governance. Projects without governance risk misalignment, unmanaged scope creep, and budget overruns. Some structure is always necessary.
Static governance. The governance structure appropriate at project kickoff may not be appropriate three months later. Adjust governance as the project evolves — lighter governance during stable execution, heavier governance during risk events or major transitions.
Governance Documentation
Document the governance structure in the project charter or project kickoff materials:
- Decision authority matrix (who can decide what)
- Escalation paths (how issues move up the chain)
- Reporting cadence (who receives what information when)
- Review checkpoints (when governance reviews happen)
- Change authority (who approves scope changes of different sizes)
Keep the document short — one to two pages. Governance documentation that nobody reads does not improve governance.
The Minimum Viable Governance
For most agile projects, minimum viable governance includes:
- A named project sponsor with budget and scope authority
- A Product Owner with backlog priority authority
- Regular sprint reviews where stakeholders inspect and direct
- A change process for scope changes exceeding team authority
- Monthly status reports to the sponsor
This structure provides accountability, direction, and transparency without creating the bureaucratic overhead that slows agile teams. Add additional governance mechanisms only when specific risk, compliance, or organizational requirements demand them.