Recipes for Agile Governance in the Enterprise (RAGE)

Large enterprises need governance to make decisions about what work to undertake, how to prioritize it, how to coordinate work across teams and business units, and when to change direction. Traditional governance approaches can become cumbersome, particularly when an organization contains multiple business units and multiple development processes.

Recipes for Agile Governance in the Enterprise (RAGE) presents a practical framework for designing governance that is both disciplined and adaptable. The paper introduces the concept of Agile governance as a style of decision-making that emphasizes rapid adaptation, lightweight artifacts, collaboration, and clearly defined decision authority. Importantly, Agile governance does not require every project or team to use an Agile development process; it can also support organizations operating with hybrid combinations of Agile and traditional processes.

The framework examines governance at three levels—Portfolio, Program, and Project—and describes practical roles, ceremonies, artifacts, metrics, and governance points appropriate to each. At the program level, for example, the paper describes Release Planning and cross-team coordination; at the portfolio level, it addresses business cases, prioritization, decision matrices, funding, and ongoing decisions about whether to continue, modify, or terminate initiatives.

The paper concludes by identifying broader principles and anti-patterns that can be applied beyond the specific examples presented. These include maintaining clear roles and decision authority, using meaningful measures of completed deliverables, avoiding unnecessary precision in uncertain estimates, maintaining stable teams, and treating complex handoffs as collaborative processes rather than simple transfers of documentation.

Although the paper uses a synthetic case study of a large enterprise to illustrate its ideas, its purpose is broader: to provide reusable patterns for designing effective governance in organizations where multiple teams, products, business units, and development processes must work together. The paper's practical framework became a foundation for the author's subsequent work on Agile Project, Program, and Portfolio Management.