3 Core Principles and Values of Agile

Learning Objectives

You will be able to:

Trace transparency, collaboration, adaptability, and customer-centricity to their roots in the Agile Manifesto.
Explain why transparency depends on psychological safety rather than on visibility alone.
Distinguish genuine collaboration from copied structure, using the Spotify model as an illustration.
Apply the four principles together to evaluate or redesign an HR practice.

3.1 Introduction

The Agile Manifesto (Kent Beck et al., 2001) compresses into four value statements and twelve principles. Agile HR distils that same spirit into four working principles that repeat across every serious account of the field: transparency, collaboration, adaptability, and customer-centricity. Each traces directly to the manifesto, translated from software delivery into people practice.

None of the four functions well alone. Transparency without psychological safety produces silence dressed up as openness. Collaboration without structure produces meetings, not outcomes. Adaptability without discipline produces chaos rather than responsiveness. Customer-centricity without the other three produces surveys nobody acts on. The rest of this chapter treats each principle in turn, then shows how they reinforce one another in practice.

flowchart TD
    M["Agile Manifesto:<br>four values, twelve principles"] --> T["Transparency"]
    M --> C["Collaboration"]
    M --> A["Adaptability"]
    M --> U["Customer-Centricity"]
    style M fill:#e8eaf6,stroke:#5C6BC0
    style T fill:#e3f2fd,stroke:#1976D2
    style C fill:#e8f5e9,stroke:#388E3C
    style A fill:#fff8e1,stroke:#F9A825
    style U fill:#ede7f6,stroke:#7E57C2

3.2 Transparency

3.2.1 What Transparency Means in Agile HR

Transparency in agile practice means making the real state of work visible: what is being done, what is blocked, and what is not going well, to everyone who needs to act on that information, not only to those with authority over it. Natal Dank & Riina Hellström (2020) treat visible work, an open backlog rather than a private plan held by a manager, as one of the clearest markers separating an HR function that has adopted agile ways of working from one that has only adopted agile vocabulary.

Transparency is frequently narrowed to mean open salary bands or published pay ranges. Pay transparency is one application of the principle, not its definition. The broader claim is that decisions, priorities, and problems should be visible by default, and hidden only when a specific reason requires it, rather than the reverse.

3.2.2 The Psychological Safety Foundation

Visibility alone does not produce honest information. Amy Edmondson (1999) shows, in a study of hospital and manufacturing teams, that teams differ sharply in how willing members are to report errors, ask questions, or raise concerns, and that this willingness depends on psychological safety: a shared belief that the team is safe for interpersonal risk-taking. Teams with low psychological safety did not have fewer problems; they had fewer problems reported.

Edmondson: Psychological Safety Is Not the Same as Trust

Amy Edmondson (1999) distinguishes psychological safety from simple team cohesion or agreeableness. A psychologically safe team is not one where people are unfailingly nice to each other; it is one where a member can point out a mistake, disagree with a superior, or admit uncertainty without expecting punishment or humiliation for doing so. Comfort and safety are not synonyms: a team can be safe and still argue vigorously.

The implication for Agile HR is direct. Publishing a dashboard or opening a backlog creates the opportunity for transparency; it does not create the behaviour. If raising a blocked task or an early warning carries a visible cost, reporting quietly stops, and the dashboard shows a false picture of calm.

flowchart LR
    subgraph LOW ["Transparency Without Safety"]
        L1["Information is shared<br>but risk stays high"] --> L2["People filter what<br>they report upward"]
    end
    subgraph HIGH ["Transparency With Safety"]
        H1["Information is shared<br>and risk is low"] --> H2["People surface problems<br>while they are still small"]
    end
    style L1 fill:#ffebee,stroke:#C62828
    style L2 fill:#ffebee,stroke:#C62828
    style H1 fill:#e8f5e9,stroke:#388E3C
    style H2 fill:#e8f5e9,stroke:#388E3C

3.2.3 Transparency in Practice

Stefan Strohmeier (2020) notes that digital HR platforms can be used operationally, to automate what was previously paper-based, or transformationally, to make real-time information available to everyone who needs it. A transparent HR function favours the second use: open hiring pipelines visible to the whole panel, engagement data shared with teams rather than filtered into an executive summary, and roadmaps for HR products published before they are finished.

Practitioner Insight: Model It Before You Mandate It

Employees calibrate psychological safety by watching what happens the first few times someone takes a visible risk, not by reading a values statement. A manager who thanks the person who flags a problem, publicly and without deflection, does more to establish transparency than any policy document.

Common Misconception: Transparency Means Everyone Agrees

Because transparent teams surface disagreement openly, they can look, from the outside, less harmonious than teams that keep conflict private. The opposite is usually true. A team practising real transparency argues about the work in the open and resolves it there; a team without it argues about the work in private, after the meeting, where the disagreement never gets addressed.

3.3 Collaboration

3.3.1 Cross-Functional and Squad-Based Working

Agile collaboration replaces functional silos, recruitment here, learning there, reward somewhere else, with small, cross-functional groups organized around an outcome. Spotify popularized the vocabulary widely borrowed for this: squads as the basic autonomous team, tribes as collections of related squads, and chapters and guilds as the horizontal threads that keep a discipline, such as engineering practice or, by extension, an HR specialism, consistent across squads. ING’s own reorganization into squads and tribes drew explicitly on this model (Stephen Denning, 2018).

Common Misconception: Copying the Chart Copies the Culture

The Spotify model is one of the most imitated organizational diagrams in industry, and one of the most frequently misapplied. Organizations that adopt the squad-and-tribe labels without the underlying autonomy, trust, and psychological safety that made the model work typically end up with new job titles layered over the old reporting lines and decision rights. The structure is not the mechanism; the mechanism is the degree of genuine autonomy a squad actually holds.

3.3.2 Collaboration Requires Structure, Not Just Goodwill

Darrell K. Rigby et al. (2020) caution against treating collaboration as a cultural aspiration achievable through goodwill alone. Effective cross-functional collaboration needs deliberate structural support: shared goals that make cooperation rational rather than optional, protected time for joint work, and, critically, decision rights that are actually delegated to the group rather than merely described as delegated. Without that structure, cross-functional teams default back to the reporting lines that actually control resources and evaluation.

Collaboration Old and New

Dimension	Siloed Model	Agile Collaboration
Team composition	Single function, single manager	Cross-functional, shared outcome
Coordination mechanism	Escalation up the hierarchy	Direct peer coordination
Decision rights	Held by function heads	Delegated to the working group
Failure mode	Hand-off delay and blame	Diffuse accountability if rights are not clear

3.4 Adaptability

3.4.1 Responding to Change over Following a Plan

The Agile Manifesto’s fourth value, responding to change over following a plan (Kent Beck et al., 2001), is the principle most directly opposed to conventional HR planning, where a workforce plan or a competency framework is often treated as a commitment to defend rather than a hypothesis to test. Adaptability means treating the plan as the current best guess, to be revised the moment better evidence arrives, not as a promise that revision would break.

3.4.2 Building Adaptive Capacity in HR Teams

Adaptability is a capability, not merely an attitude. Katharina Harsch & Marion Festing (2020) find that the HR functions best able to respond to a shifting environment are those with dynamic routines already in place for sensing gaps and reallocating people and effort, rather than those that simply intend to be flexible when the need arises. Building that capacity in advance, rather than improvising it under pressure, is what separates an adaptable function from one that is merely willing.

Practitioner Insight: Small Batches Make Adaptability Cheap

Adaptability is easiest to sustain when work is already broken into small pieces. Revising a six-week pilot after week two costs little; revising a two-year strategic workforce plan after month two costs a great deal, in sunk investment and in the political capital already spent defending it. The size of the commitment, not the willingness of the people involved, usually determines how adaptable an organization can actually be.

Common Misconception: Adaptability Means No Plan

Responding to change is sometimes read as licence to abandon planning altogether. Darrell K. Rigby et al. (2020) argue the opposite: agile teams plan constantly, in short cycles, so that each plan is cheap enough to discard when the evidence changes. The absence of planning is not agility; it is merely improvisation without the evidence step that would make it useful.

3.5 Customer-Centricity

3.5.1 The Employee as Customer

Customer-centricity asks HR to treat the employee using its services, a candidate, a new hire, a manager running a performance conversation, as a customer whose experience of the product matters as much as the product’s formal correctness. Jacob Morgan (2017) documents organizations that redesigned people processes only after mapping them from the employee’s point of view and discovering friction invisible from the HR function’s own vantage point. Ben Whitter (2019) states the underlying instruction plainly: design the work around the human being, not the human being around the process.

3.5.2 Designing HR Products Around User Needs

Emma Bridger & Belinda Gannaway (2021) frame every HR offering, an onboarding journey, a benefits portal, a review process, as a product with users, and argue it should be designed, tested, and iterated the way a product team would treat a customer-facing feature: starting from a real user’s problem rather than from administrative convenience. This stands in useful contrast to the strategic HRM era described by David Ulrich (1997), where the HR professional’s primary client relationship was with business leadership; customer-centricity extends that client relationship down to every employee the function touches.

The Four Principles at a Glance

Principle	Manifesto Root	Traditional HR Default	Agile HR Practice
Transparency	Individuals and interactions over process	Information filtered upward through hierarchy	Visible backlogs, open data, safety to report problems (Amy Edmondson, 1999)
Collaboration	Customer collaboration over contract negotiation	Functional silos coordinated by escalation	Cross-functional squads with delegated decision rights
Adaptability	Responding to change over following a plan	Plans defended once approved	Short cycles; plans revised on evidence (Katharina Harsch & Marion Festing, 2020)
Customer-centricity	Working software over documentation	Processes designed for administrative convenience	Employee journeys designed and tested like a product (Emma Bridger & Belinda Gannaway, 2021)

3.6 How the Four Principles Work Together

The four principles are not a checklist to complete independently. Transparency without collaboration surfaces a problem nobody is positioned to fix. Collaboration without adaptability builds strong cross-functional relationships that still defend a stale plan together. Adaptability without customer-centricity can produce a function that changes constantly without ever changing in a direction employees value. Customer-centricity without transparency collects employee feedback that never becomes visible enough to act on. Each principle supplies something the others need.

flowchart LR
    T["Transparency"] --> C["Collaboration"]
    C --> A["Adaptability"]
    A --> U["Customer-Centricity"]
    U --> T
    style T fill:#e3f2fd,stroke:#1976D2
    style C fill:#e8f5e9,stroke:#388E3C
    style A fill:#fff8e1,stroke:#F9A825
    style U fill:#ede7f6,stroke:#7E57C2

3.7 Case Studies

3.7.1 Case Study 1: Buffer, Radical Transparency as Policy

Buffer, a social media management company, has published every employee’s salary, along with the formula used to calculate it, since 2013, and maintains a public transparency dashboard covering revenue, equity, and diversity data alongside compensation. The company has revised its salary formula multiple times in response to employee and public feedback, treating the formula itself as a product to iterate rather than a policy fixed at launch.

Discussion Questions:

What organizational conditions would make public salary transparency workable, and what conditions would make it destructive?
How does Buffer’s willingness to revise its formula in public illustrate transparency and adaptability reinforcing each other?
What psychological safety risks does radical pay transparency introduce that a private pay structure does not?

3.7.2 Case Study 2: Netflix, Freedom and Responsibility

Netflix’s long-standing culture memo, built around the principle of “freedom and responsibility,” replaced detailed policy, including a formal vacation policy and expense approval limits, with a smaller set of high-trust guidelines and an expectation of candid, direct feedback. The company has periodically revised the memo itself, including a 2024 update, treating its own culture statement as a living document rather than a fixed artefact.

Discussion Questions:

What must be true of hiring and performance management for a low-policy, high-trust model like Netflix’s to function without abuse?
How does replacing detailed policy with guidelines shift risk between the employee and the organization?
Would Netflix’s model transfer to a highly regulated industry? What would have to change?

3.7.3 Case Study 3: Spotify, Collaboration Through Squads and Guilds

Spotify’s internal engineering organization popularized the squad, tribe, chapter, and guild vocabulary now widely referenced in agile collaboration design: small autonomous squads for delivery, tribes grouping related squads, and chapters and guilds preserving craft consistency and knowledge-sharing across squad boundaries. Spotify itself has since acknowledged that the model as publicly described was never a fixed blueprint even inside the company, and that the autonomy and trust underlying it matter more than the specific labels.

Discussion Questions:

Why might an organization that copies Spotify’s structural labels fail to reproduce Spotify’s results?
What decision rights would a squad need to hold in practice for the label “autonomous” to be more than nominal?
How do chapters and guilds address a risk that pure squad-based collaboration creates on its own?

3.8 Summary

Chapter Summary

Agile HR’s four core principles, transparency, collaboration, adaptability, and customer-centricity, trace directly to the Agile Manifesto’s values (Kent Beck et al., 2001). Transparency requires psychological safety to function, since visibility alone does not make people willing to report bad news (Amy Edmondson, 1999). Collaboration requires delegated decision rights, not only goodwill or a copied org chart (Darrell K. Rigby et al., 2020). Adaptability is a built capability, sustained by short cycles and dynamic routines, not an attitude summoned under pressure (Katharina Harsch & Marion Festing, 2020). Customer-centricity treats every HR offering as a product designed around the employee who uses it (Emma Bridger & Belinda Gannaway, 2021; Jacob Morgan, 2017).

Buffer, Netflix, and Spotify each illustrate one principle prominently, radical transparency, low-policy adaptability, and structured collaboration, while showing that no principle survives long in isolation from the other three.

Key Terms

Transparency · Psychological safety · Collaboration · Cross-functional squad · Spotify model · Adaptability · Dynamic capability · Customer-centricity · Employee as customer · HR product

Summary

Concept	Description
Transparency
Transparency	Making the real state of work visible by default to everyone who needs to act on it
Psychological safety	A shared belief that a team is safe for interpersonal risk-taking such as admitting error or disagreement
Pay transparency	One application of transparency, publishing pay ranges or formulas, not the principle's full definition
Collaboration
Collaboration	Small, cross-functional groups organized around an outcome rather than a function
Cross-functional squad	An autonomous, outcome-focused team drawing members from multiple functions
Spotify model	The squad, tribe, chapter, and guild vocabulary popularized by Spotify's engineering organization
Delegated decision rights	Authority actually transferred to a working group, rather than merely described as transferred
Adaptability
Adaptability	The capability to revise plans and practices quickly as evidence changes
Dynamic capability	The organizational routine that lets a function sense and act on a capability gap quickly
Short-cycle planning	Planning in small, cheap-to-revise increments rather than long, costly-to-abandon commitments
Customer-Centricity
Customer-centricity	Treating HR services as products whose users' experience matters as much as their formal correctness
Employee as customer	Viewing every person who interacts with an HR process, not only leadership, as a client of the function
HR product thinking	Designing, testing, and iterating HR offerings the way a product team treats a customer-facing feature
Case Evidence
Buffer's transparent salary formula	Buffer's practice of publishing every salary and the formula behind it since 2013
Netflix freedom and responsibility	Netflix's high-trust, low-policy culture doctrine, periodically revised rather than fixed
Spotify squads and guilds	Spotify's cross-functional collaboration structure, often copied for its labels without its underlying autonomy