← Back to the blog

Blog

Agile Projects: Governance Without Role Confusion

Agile projects rarely fail because a team has too little freedom. Unclear governance is the bigger risk. Who sets functional priorities, who protects the working process, who owns budget, security and suppliers, and who decides when those interests conflict?

On 2 November, GPM and ITZBund published a practice article that deliberately describes something other than “pure Scrum” for Germany’s federal administration. The model adds project management as a strategic bridge alongside the Product Owner, Scrum Master and Developers. It coordinates higher-level bodies, resources and binding constraints, and it can intervene selectively in critical planning and review situations.

Agility does not remove accountability

The Scrum Guide defines three clear accountabilities within the Scrum Team, but no traditional project manager. That works when the wider organisation explicitly governs budget, compliance, contracts and escalation. Where that arrangement is missing, shadow roles appear. The Product Owner is suddenly expected to manage suppliers, the Scrum Master has to obtain approvals, and the steering committee intervenes unpredictably in individual Sprints.

ITZBund therefore combines agile development with V-Modell XT and places particular weight on three areas:

  • Functional prioritisation: The Product Owner decides on product value and order.
  • Ability to deliver: The Scrum Master removes impediments and needs to know the internal organisation to do so.
  • Project governance: Project management keeps budget, security requirements, external dependencies and resources under control.

This separation becomes especially important when external suppliers are involved. Self-management must not blur acceptance, contractual consequences and escalation rights.

A practical pattern for software projects

Before the first Sprint, I would approve a one-page governance matrix. It names the decision-maker, the contributors, the deadline and the escalation path for prioritisation, architecture deviations, security findings, budget changes, UAT acceptance and supplier escalation.

The steering report can then no longer stop at “the Sprint is progressing”. A UAT triage should show open critical defects along with the functional owner, the acceptance criterion and the contractual impact. Deviations belong in a decision log, not in informal side agreements.

What project sponsors should do now

In your next agile initiative, review the decision boundaries before you debate methodology. Where may the team act autonomously? Which few intervention rights does project management need? Which decision must never be left hanging between Product Owner, Scrum Master and sponsor?

Agility does not need a weaker framework. It needs a clear one that rarely has to intervene in daily work.

← Back to the blog