Skip to content

Enterprise-Aware Agility

Definition

Most agile guidance assumes small teams working on bounded problems. DAD explicitly addresses the reality that teams operate within larger organizational contexts where multiple projects are underway, shared infrastructure and data sources exist, governance frameworks are in place, and architectural coherence matters. Enterprise-aware agility means teams actively seek to understand and work with enterprise architects, portfolio managers, operations staff, data administrators, and security experts—not as constraints to work around, but as collaborators whose insights reduce risk and increase organizational benefit.

In the Book

Chapter 1 introduces this principle under "Enterprise Aware." The book frames it as "disciplined agilists act locally and think globally." Teams cannot operate in a vacuum; they must engage with:

  • Enterprise technical architects and reuse engineers to understand the "to be" infrastructure vision and reuse existing, proven components rather than rebuilding solutions from scratch.
  • Enterprise business architects and portfolio managers to ensure the project fits into the overall business ecosystem and aligns with organizational strategy.
  • Senior managers governing the organization to support appropriate governance without strangling agility.
  • Operations and DevOps staff to collaborate on deployment, support, and operational readiness—not hand off problems post-release.
  • Data administrators to leverage and improve existing data sources rather than creating isolated data silos.
  • IT development support to follow enterprise coding, UI, security, and data conventions, increasing consistency and reducing maintenance burden.
  • Business experts who share market insights, sales forecasts, and customer context.

The book emphasizes "whole enterprise mindset": teams should strive to leave the organizational ecosystem better than they found it. This includes knowledge-sharing—learning from other teams' experiences and contributing their own insights to internal discussion forums, wikis, and centers of competency (later called centers of excellence).

The book also illustrates the cost of not being enterprise-aware: teams that build from scratch when components already exist, use non-standard technologies, create incompatible data sources, and produce solutions that don't integrate with production infrastructure. These decisions feel fast and autonomous in the moment but create technical debt and operational chaos at scale.

Why It Matters

Enterprise-aware agility bridges the gap between agile's collaborative, adaptive nature and the organizational reality that consistency, reuse, and shared vision matter. It prevents the "agile anarchy" pattern where many small teams thrash independently, creating a portfolio of incompatible solutions. It also legitimizes governance and architecture as enablers of agility rather than obstacles—an enterprise architecture that is well-designed reduces decision friction for teams; a portfolio vision that is clear gives teams strategic context for trade-offs. For large organizations, this is the difference between agile scaling that increases organizational capability and agile adoption that fragments it.