Distributed Agility Dimensions

Definition

Distributed Agility Dimensions is a multi-level framework decomposing agility into three broad categories—resource-based, process-based, and linkage-based—and further into eight specific sub-types. Each addresses distinct challenges in geographically and temporally dispersed teams: (1) people-based agility (acquiring and reconfiguring skilled personnel across locations), (2) communication-based agility (maintaining awareness and connectivity among distributed members), (3) methodology-based agility (adapting development practices to the distributed context), (4) time-related agility (collaborating without temporal delays), (5) technology-based agility (accessing quality tools regardless of location), (6) work-transition agility (seamless handoffs across sites), (7) environmental-scanning agility (anticipating and reacting to external changes), and (8) culture-related agility (working across cultural differences). Expert practitioners ranked people and communication as far more critical than the others.

In the Book

Sarker et al. conducted an Analytic Hierarchy Process (AHP) study with six international distributed software development experts, asking them to pairwise-compare agility sub-types against three project success measures: on-time delivery, within-budget delivery, and effective collaboration. The ranking revealed: people-based (highest), communication-based, methodology-based, time-based, technology, work-transition, environmental, and cultural (lowest). Experts explained that people-based agility's salience derives from the need to rapidly acquire skilled staff at each location and "reconfigure the team on demand by rotating and shifting different team members." Communication-based agility ranked second because "geographical and temporal distance" make communicative linkages between stakeholders "even more critical." The study also provided specific tactics for each dimension: for people-based, rotate personnel across locations to disseminate knowledge; for communication-based, appoint key individuals at each location for daily updates and assign selected members to physical proximity with clients.

Why It Matters

This framework rejects the assumption that "agility" is a single scalar property. Instead, it shows that distributed teams need to build capability on multiple independent fronts, each with its own failure modes and interventions. A team might excel at technology-based agility (high-quality tools everywhere) yet collapse on communication-based agility (no real-time awareness). The prioritization—placing people and communication far above technology—contradicts the common industry focus on tool investment. It demonstrates that organizational and human factors, not infrastructure alone, determine distributed agility success. This framework also exports to non-software domains facing distribution: any knowledge work requiring coordination across distance and time must address these same dimensions.