Team Context Understanding

Definition

Context is the third critical element of an agile team charter. It involves helping a team understand how it fits into the larger organization, how its stakeholders fit into the system, and what resources and constraints it operates within. Context awareness makes implicit organizational dynamics explicit so the team can anticipate and navigate them rather than be surprised or derailed by them.

In the Book

Larsen and Nies emphasize that context is the least stable of the three charter elements—it is continuously being created and recreated every day as organizational conditions shift. Yet making it explicit during liftoff prevents teams from operating under false assumptions about what they can and cannot do.

Being aware of context involves three parts: (1) looking at the team's boundaries and interactions with other teams and stakeholders; (2) identifying the nonhuman resources committed to the work (tools, infrastructure, budget, office space); and (3) forecasting with a prospective analysis—looking ahead and checking assumptions that might prove wrong.

The Team Restart case study (Chapter 1) illustrates context challenges: teams that were not colocated, teams of different sizes, teams with perceived inequitable skill distribution, and managers who had not been communicated with about the restructuring exercise. By running a liftoff event that surfaced these context issues, the organization could address them before they undermined team performance.

The SAPHIR case study shows deliberate context clarification: the workshop explicitly addressed (1) who the customer contact persons were and what decision-making authority they held; (2) constraints on schedule and budget; (3) which team members had prior experience with the customer; and (4) quality assurance requirements and tools. One session focused entirely on customer interface management and risk identification—making visible the context that would shape daily work.

The book notes that understanding context "helps the team see the system it works in and how its stakeholders fit into the system, too." This includes understanding role clarity: who decides what, who influences whom, what approval is required for different decisions. When these are left implicit, teams waste energy navigating political minefields; when made explicit, they can be discussed and managed.

Context also includes understanding the organization's political climate, culture, and values. The book recommends that the liftoff planning group include people who know "the organizational values, the culture, and the political climate."

Why It Matters

Teams that do not understand their organizational context often pursue work in ways that create friction with stakeholders, miss important constraints, or make decisions that need to be remade because of unstated organizational rules. By making context explicit during liftoff, teams can negotiate resource commitments upfront, clarify decision authority, and understand which organizational dynamics they need to work with (rather than fight). This prevents the team from being derailed midway by discovering that a "decision" they made was actually the prerogative of an executive, or that a resource they counted on is not actually available.