domain governance Commons: 4/5

Agile Governance - IT Governance Frameworks

Also known as: Agile IT Governance, Lean Governance

1. Overview

Agile governance is a framework that applies the principles of agile software development to the practice of governance, particularly within the realm of information technology. It represents a shift away from traditional, rigid, and hierarchical governance models toward a more flexible, adaptive, and collaborative approach. The core problem that agile governance seeks to solve is the inability of traditional governance structures to keep pace with the rapid changes and uncertainties inherent in modern digital environments. By embracing agility, organizations can make more timely and informed decisions, better manage risks, and optimize the value delivered by their IT initiatives. The origin of agile governance can be traced back to the Agile Manifesto, which was created in 2001 by a group of software developers. While the manifesto was initially focused on software development, its principles have since been applied to a wide range of other domains, including project management, product development, and, more recently, governance. The need for a more agile approach to governance has become increasingly apparent as organizations have adopted agile development methods and have struggled to reconcile them with their existing governance frameworks. [1]

2. Core Principles

Agile governance is founded on a set of core principles that guide its implementation and practice. These principles are derived from the Agile Manifesto and have been adapted to the context of governance. They are designed to foster a culture of collaboration, empowerment, and continuous improvement.

  1. Effective Team Collaboration. Agile governance emphasizes the importance of collaboration between all stakeholders, including business leaders, IT professionals, and end-users. It seeks to break down silos and foster a culture of shared ownership and responsibility. By working together, teams can make better decisions, solve problems more effectively, and deliver greater value to the organization. [2]

  2. Mirror the Agile Manifesto. Agile governance embraces the values and principles of the Agile Manifesto, such as individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. By aligning with these principles, organizations can create a more adaptive and responsive governance framework that is better suited to the demands of the digital age. [2]

  3. Monitor Performance Metrics. Agile governance relies on the use of empirical data to track and measure performance. By collecting and analyzing data on key metrics, such as lead time, cycle time, and customer satisfaction, organizations can gain insights into the effectiveness of their governance processes and identify areas for improvement. This data-driven approach enables a “fail fast, learn fast” mentality, where teams are encouraged to experiment, learn from their mistakes, and continuously improve. [2]

  4. Focus on Team Behavior and Practices. Agile governance recognizes that the success of any governance framework is ultimately dependent on the behavior and practices of the people who use it. It emphasizes the importance of creating a culture of trust, transparency, and empowerment, where teams are given the autonomy to make decisions and are held accountable for the outcomes. Rather than relying on traditional command-and-control mechanisms, agile governance focuses on coaching, mentoring, and facilitating to help teams develop the skills and mindset they need to succeed. [2]

3. Key Practices

Agile governance is not just a set of principles; it is also a collection of key practices that help organizations put those principles into action. These practices are designed to be lightweight and flexible, and they can be adapted to the specific needs and context of each organization.

  1. Align organizational needs with agile projects through clear documentation. While agile governance values working software over comprehensive documentation, it does not eliminate the need for documentation altogether. Instead, it advocates for a more lightweight and focused approach to documentation, where the goal is to provide just enough information to ensure that everyone is aligned and working toward the same goals. This might include creating a project charter, a product roadmap, or a set of user stories.

  2. Continuously report new value after each iteration. Agile governance emphasizes the importance of delivering value to the business in small, incremental steps. By delivering working software at the end of each iteration, teams can get feedback from stakeholders early and often, and they can make adjustments to their plans as needed. This iterative approach helps to reduce risk, increase transparency, and ensure that the team is always working on the most valuable features.

  3. The product owner should share updates from stakeholders with the delivery team. The product owner plays a critical role in agile governance, as they are responsible for representing the interests of the stakeholders and for ensuring that the team is building the right product. To be effective, the product owner must have a deep understanding of the business and the market, and they must be able to communicate the vision and goals of the project to the team.

  4. Use agile project software to provide access to information for all stakeholders. There are a number of software tools available that can help organizations to implement agile governance. These tools can be used to manage the product backlog, track progress, and facilitate communication and collaboration among team members. By using a shared tool, everyone on the team can have access to the same information, which helps to improve transparency and alignment.

  5. Welcome changes throughout the project. One of the key principles of agile is the ability to respond to change. In a traditional project management approach, change is often seen as a negative thing that should be avoided. In an agile approach, however, change is seen as an opportunity to learn and improve. By embracing change, organizations can ensure that they are always building the most valuable product for their customers.

4. Application Context

Agile governance is not a one-size-fits-all solution. It is best suited for certain types of organizations and projects, and it may not be appropriate for others. Understanding the application context of agile governance is essential for its successful implementation.

Best Used For:

  • Organizations with a high degree of uncertainty and complexity. Agile governance is well-suited for environments where requirements are constantly changing and where there is a high degree of uncertainty about the future. Its iterative and adaptive nature allows organizations to respond to change quickly and effectively.
  • Organizations that are undergoing a digital transformation. As organizations adopt new technologies and business models, they often find that their traditional governance structures are no longer adequate. Agile governance can provide a more flexible and responsive framework for managing the risks and opportunities associated with digital transformation.
  • Organizations that have adopted agile development methods. Agile governance is a natural complement to agile development methods, as it provides a framework for aligning the work of development teams with the strategic goals of the organization.
  • Projects with a high degree of innovation. When working on innovative projects, it is often difficult to define all of the requirements upfront. Agile governance allows teams to start with a high-level vision and then to elaborate on the details as they learn more about the problem and the solution.
  • Government and public sector organizations. As demonstrated by the case studies from the OECD, agile governance is being increasingly adopted by government and public sector organizations to improve the delivery of public services and to foster innovation. [3]

Not Suitable For:

  • Organizations with a low tolerance for risk. Agile governance embraces a “fail fast, learn fast” mentality, which may not be appropriate for organizations that have a low tolerance for risk. In these cases, a more traditional, risk-averse approach to governance may be more appropriate.
  • Projects with well-defined requirements and a stable environment. If the requirements for a project are well-defined and the environment is stable, there may be little to be gained by using an agile approach to governance. In these cases, a more traditional, plan-driven approach may be more efficient.

Scale:

Agile governance can be applied at all levels of an organization, from individual teams to the entire enterprise. It can be used to govern a single project or a portfolio of projects. The principles of agile governance are fractal, meaning that they can be applied at different scales with similar results.

Domains:

Agile governance is most commonly applied in the information technology domain, but it can also be used in other domains, such as product development, marketing, and even legal and finance. Any domain that is characterized by a high degree of uncertainty and complexity can benefit from an agile approach to governance.

5. Implementation

Implementing agile governance requires a thoughtful and deliberate approach. It is not something that can be done overnight. It requires a change in mindset, a commitment from leadership, and a willingness to experiment and learn.

Prerequisites:

  • Leadership Buy-in: The most important prerequisite for implementing agile governance is strong and visible support from leadership. Leaders must be willing to champion the change, to provide the necessary resources, and to model the desired behaviors.
  • A Culture of Trust and Transparency: Agile governance thrives in a culture of trust and transparency. Teams must feel safe to experiment, to take risks, and to learn from their mistakes. There must be open and honest communication among all stakeholders.
  • A Basic Understanding of Agile Principles: While it is not necessary for everyone in the organization to be an agile expert, it is important to have a basic understanding of the principles and values of agile. This will help to ensure that everyone is speaking the same language and working toward the same goals.

Getting Started:

  1. Start Small: It is often best to start with a small pilot project to test the waters and to learn what works best for your organization. This will help to build momentum and to gain the support of stakeholders.
  2. Form a Cross-Functional Team: The pilot project should be staffed with a cross-functional team that includes representatives from all of the key stakeholder groups. This will help to ensure that all perspectives are considered and that the team has the skills and expertise it needs to succeed.
  3. Define the Goals and Objectives: Before starting the pilot project, it is important to define the goals and objectives of the project. What are you trying to achieve? How will you measure success? Having a clear understanding of the goals will help to keep the team focused and on track.
  4. Choose a Framework: There are a number of different agile frameworks to choose from, such as Scrum, Kanban, and SAFe. It is important to choose a framework that is a good fit for your organization and your project.
  5. Provide Training and Coaching: It is important to provide training and coaching to the team to help them learn the new process and to develop the skills they need to be successful.

Common Challenges:

  • Resistance to Change: One of the biggest challenges to implementing agile governance is resistance to change. People are often comfortable with the way things are, and they may be resistant to new ideas and new ways of working.
  • Lack of Understanding: Another common challenge is a lack of understanding of what agile governance is and how it works. This can lead to confusion, frustration, and a lack of buy-in from stakeholders.
  • Inadequate Tooling: While agile governance is not about tools, having the right tools can make a big difference. Inadequate tooling can make it difficult to manage the product backlog, to track progress, and to collaborate effectively.
  • Cultural Barriers: Agile governance requires a culture of trust, transparency, and collaboration. If your organization has a more traditional, hierarchical culture, it may be difficult to implement agile governance successfully.

Success Factors:

  • Strong Leadership Support: As mentioned earlier, strong leadership support is essential for success.
  • A Clear Vision and Goals: Having a clear vision and goals will help to keep the team focused and on track.
  • A Dedicated and Empowered Team: The team must be dedicated to the project and must be empowered to make decisions.
  • A Willingness to Experiment and Learn: Agile governance is an iterative process. It is important to be willing to experiment, to learn from your mistakes, and to continuously improve.

6. Evidence & Impact

Agile governance is not just a theoretical concept; it is a practical framework that has been successfully implemented by a wide range of organizations, from small startups to large multinational corporations and government agencies. The evidence shows that agile governance can have a significant and positive impact on an organization’s ability to deliver value, to manage risk, and to respond to change.

Notable Adopters:

  • UK Civil Aviation Authority (CAA): The CAA has established an Innovation Hub and an Innovation Sandbox to help innovators to navigate the regulatory landscape and to test new technologies in a safe and controlled environment. This approach has enabled the CAA to work collaboratively with industry to develop new regulations for emerging technologies, such as drones. [3]
  • Korean Ministry of Land, Infrastructure and Transport: The Korean government has launched a “Drone Regulation Breakthrough Roadmap” with the goal of commercializing drone delivery by 2025. This initiative is a clear example of how agile governance can be used to foster innovation and to create new economic opportunities. [3]
  • Government of Canada: The Government of Canada has adopted an agile approach to the procurement of IT services. This has enabled the government to reduce the time it takes to procure new services, to improve the quality of the services it receives, and to save money.
  • ING: The Dutch multinational banking and financial services corporation has undergone a large-scale agile transformation, which has included the adoption of agile governance principles. This has enabled ING to become more customer-centric, to improve its time-to-market, and to increase employee engagement.
  • Spotify: The music streaming service is well-known for its agile culture, which is based on the principles of autonomy, alignment, and accountability. Spotify’s agile governance model has enabled it to innovate rapidly and to maintain its position as a leader in the music industry.

Documented Outcomes:

  • Increased Speed and Responsiveness: Agile governance can help organizations to reduce the time it takes to make decisions and to respond to change. This can lead to a significant improvement in time-to-market and a greater ability to seize new opportunities.
  • Improved Quality: By focusing on continuous feedback and improvement, agile governance can help organizations to improve the quality of their products and services. This can lead to increased customer satisfaction and loyalty.
  • Reduced Risk: Agile governance’s iterative and incremental approach can help organizations to reduce the risk of project failure. By delivering value in small increments, teams can get feedback early and often, and they can make adjustments to their plans as needed.
  • Increased Employee Engagement: Agile governance can help to create a more empowering and collaborative work environment. This can lead to increased employee engagement, motivation, and job satisfaction.

Research Support:

  • A 2018 study by the Project Management Institute (PMI) found that organizations that had adopted an agile approach to governance were more likely to be successful in their projects than those that had not.
  • A 2019 report by the Standish Group found that agile projects were three times more likely to be successful than traditional, waterfall projects.
  • The OECD has published a number of case studies and reports that document the successful implementation of agile governance in the public sector. [3]

7. Cognitive Era Considerations

The cognitive era, characterized by the rise of artificial intelligence (AI) and machine learning, presents both new opportunities and challenges for agile governance. As organizations increasingly leverage AI to automate tasks, gain insights from data, and enhance decision-making, the principles and practices of agile governance will need to evolve to keep pace.

Cognitive Augmentation Potential:

AI and automation have the potential to significantly augment agile governance in a number of ways. For example, AI-powered tools can be used to automate the collection and analysis of performance data, providing teams with real-time insights into their progress and helping them to identify areas for improvement. AI can also be used to automate compliance checks, freeing up teams to focus on more value-added activities. In the future, we may even see AI-powered agents that can participate in governance meetings, providing data-driven recommendations and helping to facilitate decision-making.

Human-Machine Balance:

As AI and automation become more prevalent, it will be important to strike the right balance between human and machine intelligence. While AI can be a powerful tool for augmenting agile governance, it is not a replacement for human judgment and intuition. There will always be a need for human oversight and intervention, particularly when it comes to making complex ethical and strategic decisions. The goal should be to create a symbiotic relationship between humans and machines, where each is able to do what it does best.

Evolution Outlook:

In the cognitive era, agile governance is likely to become even more important than it is today. As the pace of change continues to accelerate, organizations will need to be able to adapt quickly and effectively to new challenges and opportunities. Agile governance provides a framework for doing just that. In the future, we are likely to see a greater emphasis on data-driven decision-making, continuous learning, and experimentation. We may also see the emergence of new agile governance frameworks that are specifically designed for the cognitive era.

8. Commons Alignment Assessment (v2.0)

This assessment evaluates the pattern based on the Commons OS v2.0 framework, which focuses on the pattern’s ability to enable resilient collective value creation.

1. Stakeholder Architecture: Agile Governance defines a stakeholder architecture focused on human actors within an organization, primarily business leaders, IT professionals, and end-users. It establishes Rights and Responsibilities through collaborative practices and shared ownership, breaking down traditional hierarchical structures. However, the framework does not explicitly extend its stakeholder considerations to non-human agents like the environment, AI systems, or future generations, which is a key aspect of a complete Commons architecture.

2. Value Creation Capability: The pattern strongly enables collective value creation by focusing on delivering incremental value and continuously incorporating stakeholder feedback. This process creates knowledge value and enhances the social value of collaboration within the organization. While the primary focus is on business and customer value, the iterative and adaptive nature of the framework can be extended to optimize for ecological or other forms of non-economic value.

3. Resilience & Adaptability: Resilience and adaptability are at the core of Agile Governance. The pattern is explicitly designed to help systems thrive on change, adapt to complexity, and maintain coherence in uncertain environments. Practices like iterative development, continuous reporting, and embracing change allow the system to learn and evolve, making it highly resilient to internal and external stressors.

4. Ownership Architecture: Agile Governance shifts the concept of ownership from a rigid, top-down model to one of distributed responsibility and stewardship. The Product Owner acts as a steward for stakeholder interests, and the entire team shares ownership of the outcomes. This defines ownership as a set of Rights and Responsibilities for value creation, rather than being based on monetary equity or control over resources.

5. Design for Autonomy: The pattern is well-suited for autonomous systems. It empowers decentralized teams with the autonomy to make decisions and self-organize, reducing coordination overhead. Its principles of lightweight documentation and focusing on interactions over rigid processes make it compatible with the operational logic of DAOs and AI-driven systems that require flexibility and adaptability.

6. Composability & Interoperability: Agile Governance is highly composable. It is a meta-framework that can be combined with various other agile methods like Scrum or Kanban to create tailored governance systems. Its principles are domain-agnostic and can be applied to various contexts, allowing it to interoperate with other organizational patterns to build larger, more complex value-creation systems.

7. Fractal Value Creation: The pattern exhibits strong fractal characteristics. The core principles of iterative value creation, stakeholder collaboration, and adaptation can be applied at multiple scales, from a single project team to an entire enterprise portfolio. This allows the value-creation logic to be replicated and scaled throughout an organization, creating a coherent governance structure across different levels.

Overall Score: 4 (Value Creation Enabler)

Rationale: Agile Governance is a powerful enabler of collective value creation, demonstrating strong alignment with most of the v2.0 pillars, particularly Resilience, Autonomy, and Composability. It provides a robust framework for adaptive and collaborative decision-making. The primary reason it does not receive a score of 5 is its limited stakeholder architecture, which is primarily focused on internal, human stakeholders and does not explicitly account for broader ecological, social, or future-oriented responsibilities.

Opportunities for Improvement:

  • Explicitly integrate non-human stakeholders (e.g., environment, AI agents) into the governance process with defined Rights and Responsibilities.
  • Develop metrics for value creation that go beyond economic or business outcomes to include social, ecological, and knowledge value.
  • Create specific guidelines on how to apply the framework to steward shared resources and commons, not just internal IT projects.

    9. Resources & References

Essential Reading:

  • The Agile Manifesto (2001): The foundational document for all agile methodologies. It outlines the core values and principles that underpin agile governance.
  • “Leading the Transformation: Applying Agile and DevOps Principles at Scale” by Gary Gruver and Tommy Mouser (2015): This book provides a practical guide to implementing agile and DevOps principles at an enterprise level, including a discussion of the role of governance.
  • “Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework” by Mik Kersten (2018): This book argues for a shift from a project-based to a product-based mindset, which has significant implications for how we think about governance.

Organizations & Communities:

  • Agile Business Consortium: A not-for-profit organization that provides a wealth of resources on agile, including a framework for business agility that includes a section on agile governance. [1]
  • Agile Alliance: A global non-profit organization dedicated to promoting the concepts of Agile software development as outlined in the Agile Manifesto.
  • Project Management Institute (PMI): The world’s leading professional association for project, program and portfolio management. PMI offers a range of resources on agile, including a certification in agile project management.

Tools & Platforms:

  • Jira: A popular software application used for bug tracking, issue tracking, and project management. It is widely used by agile teams to manage their work.
  • Trello: A web-based Kanban-style list-making application. It is a simple and flexible tool that can be used to manage a wide range of projects.
  • Asana: A web and mobile application designed to help teams organize, track, and manage their work.

References:

[1] Agile Business Consortium. (n.d.). What is Agile Governance? Retrieved from https://www.agilebusiness.org/business-agility/framework-for-business-agility/agile-governance.html

[2] Agilemania. (2022, February 12). What is Agile Governance: 4 Guiding Principles in Agile. Retrieved from https://agilemania.com/what-is-agile-governance

[3] Hernández, G., & Amaral, M. (2022). Case studies on agile regulatory governance to harness innovation. OECD. Retrieved from https://www.oecd.org/en/publications/case-studies-on-agile-regulatory-governance-to-harness-innovation_0fa5e0e6-en.html

[4] Project Management Institute. (2017). Achieving Greater Agility: The Essential Influence of the C-Suite. Retrieved from https://www.pmi.org/learning/library/achieving-greater-agility-c-suite-11130

[5] The Standish Group. (2020). CHAOS 2020: Beyond Infinity. Retrieved from https://www.standishgroup.com/sample_research_files/CHAOS2020.pdf

[6] Government of Canada. (n.d.). Agile procurement. Retrieved from https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/agile-procurement.html

[7] ING. (n.d.). How ING is transforming into an agile organization. Retrieved from https://www.ing.com/About-us/Strategy/How-ING-is-transforming-into-an-agile-organization.htm

[8] Kniberg, H., & Ivarsson, A. (2012). Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds. Retrieved from https://engineering.atspotify.com/2012/11/15/scaling-agile-at-spotify-with-tribes-squads-chapters-guilds/