1 Introduction to Agile HR

Learning Objectives

By the end of this chapter, the reader will be able to:

Define Agile HR and trace its origins in the Agile Manifesto of 2001.
Describe the four historical phases through which people management evolved, from personnel administration to Agile HR.
Explain why annual, plan-driven HR practices struggle in volatile business environments.
Recognize what changes, and what does not, when an HR function adopts agile ways of working.

1.1 Introduction

In February 2001, seventeen software developers met at a ski lodge in Snowbird, Utah, and wrote a short document that reshaped how the technology industry organizes work. The Agile Manifesto contained four value statements and twelve principles. It said nothing about human resources. Yet two decades later, HR teams from Amsterdam to Bengaluru run their work in sprints, replace annual appraisals with continuous check-ins, and reorganize themselves into cross-functional squads. Denning (2018) calls this migration of agile thinking beyond software “the age of agile”, and argues that it now defines how competitive organizations manage everything, including their people.

This chapter introduces Agile HR: what it is, where it came from, and why it emerged when it did. The concept is best understood historically. Agile HR is not a fashionable relabeling of existing practice but the fourth distinct phase in the evolution of people management, and each earlier phase, personnel administration, human resource management, and strategic HRM, solved the problems of its own era while creating the rigidities the next era had to overcome (Dank & Hellström, 2020). Understanding that lineage protects you from the most common mistake practitioners make, which is treating agility as a set of tools to install rather than a different logic of working to adopt.

The chapter sets the foundation for everything that follows in this book. Later chapters examine the drivers of agile transformation, the core agile values, and specific frameworks such as Scrum and Kanban applied to HR. Here the task is narrower: to establish clearly what Agile HR means and how we arrived at it.

Code

flowchart LR
    A["Personnel<br>Administration<br><i>1900s–1970s</i>"] --> B["Human Resource<br>Management<br><i>1980s–1990s</i>"]
    B --> C["Strategic HRM<br><i>1990s–2000s</i>"]
    C --> D["Agile HR<br><i>2010s–present</i>"]
    style A fill:#e3f2fd,stroke:#1976D2
    style B fill:#e8eaf6,stroke:#5C6BC0
    style C fill:#ede7f6,stroke:#7E57C2
    style D fill:#e8f5e9,stroke:#388E3C

flowchart LR
    A["Personnel<br>Administration<br><i>1900s–1970s</i>"] --> B["Human Resource<br>Management<br><i>1980s–1990s</i>"]
    B --> C["Strategic HRM<br><i>1990s–2000s</i>"]
    C --> D["Agile HR<br><i>2010s–present</i>"]
    style A fill:#e3f2fd,stroke:#1976D2
    style B fill:#e8eaf6,stroke:#5C6BC0
    style C fill:#ede7f6,stroke:#7E57C2
    style D fill:#e8f5e9,stroke:#388E3C

1.2 What Is Agile HR?

1.2.1 From Software Teams to People Practices

The Agile Manifesto (Beck et al., 2001) proposed four value preferences for software development: 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. The authors were careful with their wording. The items on the right retain value; the items on the left are valued more. Agile is therefore a matter of emphasis under uncertainty, not a rejection of process, documentation, or planning.

Software teams adopted these values because their old approach, the sequential “waterfall” model, kept failing them. Waterfall projects gathered all requirements up front, designed the complete system, built it, and only then showed it to users, sometimes years later, by which point needs had moved on. Agile methods inverted this: build a small piece, show it to the customer, learn, and adjust. Denning (2018) documents how this iterative logic then spread to marketing, manufacturing, and general management, because the underlying problem, planning long cycles in a fast-changing environment, was never unique to software.

HR faced exactly that problem. Consider the traditional annual performance cycle: objectives set in April, reviewed the following March. In a business where priorities shift quarterly, most of those objectives are obsolete by autumn, yet the process grinds on because the cycle, not the need, dictates the work. The same critique applies to annual engagement surveys, multi-year competency frameworks, and recruitment processes measured in months. Adams (2021) argues that much of what HR does was designed for a stable world that no longer exists, and that the function needs redesign, not refinement.

1.2.2 A Working Definition

Dank and Hellström: Agile HR Has Two Faces

Dank and Hellström (2020) draw a distinction that organizes this entire book. Agile for HR means the HR function itself adopting agile ways of working: managing its work through visible backlogs, delivering in short cycles, and testing people solutions with employees before scaling them. HR for Agile means HR redesigning its products, such as hiring, performance management, reward, and learning, so that they support agile teams and an adaptive organization rather than obstruct them. A mature Agile HR function does both.

Drawing these threads together, we can define Agile HR as the application of agile values, principles, and ways of working to the people function: iterative delivery of HR work in short cycles, co-creation of people solutions with employees as customers, decisions informed by feedback and evidence rather than by annual calendar, and a shift from controlling processes to enabling teams. The definition deliberately emphasizes logic over tooling. An HR team can hold daily stand-ups and still be profoundly non-agile if it never tests its assumptions with employees; conversely, a team that pilots a new onboarding journey with one department, learns, and revises it is doing agile work whatever it calls the meetings.

Practitioner Insight: Start with the Problem, Not the Framework

Experienced agile coaches rarely begin an HR transformation by teaching Scrum vocabulary. They begin by asking which people process causes the most frustration, then run one small experiment on it. A pilot that shortens hiring feedback loops in a single business unit teaches an HR team more about agility than a week of certification training, because it forces the team to confront real feedback from real users of its work.

Common Misconception: Agile Means Fast

Agile is frequently misread as a synonym for speed, as though Agile HR simply means doing the same HR work in less time. The aim is not speed for its own sake but shorter learning loops: delivering work in small pieces so that feedback arrives early, while change is still cheap. An agile recruitment process may not fill a role faster in every case, but it will discover far sooner that a role profile is wrong, and correcting course early is where the real gains lie. Speed is a frequent by-product of agility; it is not the definition.

1.3 The Evolution from Traditional HRM to Agile HR

The people function has reinvented itself roughly once a generation. Each phase responded to the dominant organizational problem of its time, and each left behind structures the next phase had to dismantle.

1.3.1 Personnel Administration

For most of the twentieth century, managing people meant administering them. Personnel departments emerged alongside the large industrial firm, and their concerns were transactional: hiring at the factory gate, payroll, attendance, discipline, and compliance with labour legislation. The intellectual backdrop was scientific management, with its assumption that work could be standardized and workers instructed. In India, the Factories Act of 1948 and allied welfare legislation gave the personnel officer a further statutory role, and in many Indian firms the department was, and is still sometimes, named “Personnel and Administration”. The employee in this era was a cost to be controlled, and the function’s success was measured by the absence of problems: no strikes, no compliance breaches, no payroll errors.

1.3.2 Human Resource Management

The 1980s brought a change of label that signalled a change of theory. “Human resource management” framed people as resources capable of development rather than costs to be minimized. Motivation theory and organizational behaviour entered the mainstream of practice, and the function built the machinery that most readers will recognize: structured recruitment and selection, training departments, job evaluation, performance appraisal systems, and salary structures. This was genuine progress, yet it embedded an assumption that would later become a liability, namely that good people management means comprehensive, standardized processes applied uniformly across the organization on an annual rhythm.

1.3.3 Strategic Human Resource Management

From the 1990s, scholars and practitioners pressed a further claim: HR should not merely run processes but contribute to competitive advantage. Ulrich (1997) gave the era its vocabulary, recasting HR professionals as strategic partners, change agents, administrative experts, and employee champions, and the “HR business partner” role spread through large organizations worldwide. Strategic HRM tied people practices to business strategy through workforce planning, talent management, and competency architectures. Its limitation was structural. Strategy itself was still conceived as a long-cycle artifact, formulated at the top and cascaded downward, so HR alignment inherited the same long cycles. A three-year workforce plan aligned to a three-year strategy is of limited comfort when the market shifts in six months.

1.3.4 Agile HR

The fourth phase became visible in the mid-2010s, when organizations that had adopted agile ways of working at scale found their HR machinery pulling against them. Laloux (2022) describes pioneering organizations that abandon hierarchical command structures for self-managing teams, and notes that conventional appraisal, grading, and control systems actively undermine such structures. The response, documented by Dank and Hellström (2020), was a wave of experimentation: performance management rebuilt around continuous conversations, engagement measured through frequent pulse surveys rather than annual censuses, HR teams organized as squads working from backlogs, and people policies released as iterated “products” rather than launched as final programmes. Raines (2020) adds the workforce dimension, arguing that automation and digital platforms free HR from transactional load precisely so that it can take on this adaptive role.

Four Eras Compared

Dimension	Personnel Administration	HRM	Strategic HRM	Agile HR
View of the employee	Cost to control	Resource to develop	Talent to deploy	Customer to serve and partner
Dominant rhythm	Continuous administration	Annual programmes	Multi-year planning	Short iterative cycles
Design logic	Standardization	Comprehensive process	Strategic alignment	Experimentation and feedback
Success measure	Absence of problems	Process quality	Contribution to strategy	Employee and business outcomes
Typical artifact	Attendance register	Appraisal form	Competency framework	Backlog and pulse survey

Two cautions belong to this narrative. First, the phases overlap rather than replace one another; a modern HR function still administers payroll and still aligns with strategy, and agile ways of working sit on top of, not instead of, these obligations. Second, later does not automatically mean better for every context. A small, stable manufacturing unit with low attrition may be well served by conventional practice, a point developed further when Chapter 4 contrasts agile and traditional HR directly.

1.4 Why Agile HR Matters in Modern Organizations

1.4.1 The Business Case

The environments in which organizations now operate are routinely described as volatile, uncertain, complex, and ambiguous. Product cycles have compressed, digital competitors appear without warning, and skills become obsolete faster than curricula can be redesigned. Rigby, Elk, and Berez (2020) argue that the appropriate response is not to make everything agile but to build an “agile enterprise” in which the parts of the organization facing volatility can sense and respond quickly, supported by stable backbone functions. HR sits at the hinge of that design. Team structures, hiring, incentives, and development, all of them HR products, either enable rapid reconfiguration or prevent it.

The lived experience of several large firms illustrates the stakes. When the Dutch bank ING reorganized its headquarters into tribes and squads in 2015, the transformation was as much an HR event as a technology one: thousands of employees re-interviewed for roles in the new structure, job architectures rewritten, and performance management redesigned around team outcomes (Denning, 2018). Adobe’s decision in 2012 to abolish annual performance ratings in favour of frequent “Check-In” conversations became one of the most cited HR redesigns of the decade, and was driven by an explicitly agile diagnosis: yearly feedback was arriving too late to change anything. Bock (2015) describes how Google built people decisions on continuous data and experimentation rather than annual ritual, a people-analytics sensibility that agile HR teams now treat as standard equipment.

1.4.2 The Employee Expectation Shift

The second driver is the changed expectations of the workforce itself. Morgan (2017) documents a shift in the employment relationship: employees increasingly evaluate organizations the way consumers evaluate services, attending to the whole experience of work rather than salary alone. Whitter (2019) makes the same point from the practitioner side, urging organizations to design work around the human being rather than fit the human into the process. Multi-generational workforces, hybrid work, and the visibility that platforms such as Glassdoor and LinkedIn give to employer reputations all raise the cost of rigid, impersonal people processes.

Agile HR and employee experience are, for this reason, natural partners, and their pairing gives this book its title. Iterative working supplies the method, and employee experience supplies the direction: co-creating people solutions with employees, testing them against real reactions, and improving them continuously is simply agile working pointed at the employee journey (Bridger & Gannaway, 2021). Module 4 of this book returns to employee experience in depth.

Code

flowchart TD
    A["Volatile business<br>environment"] --> C["Demand for<br>organizational agility"]
    B["Rising employee<br>expectations"] --> C
    C --> D["Agile HR:<br>iterative, co-created<br>people practices"]
    D --> E["Adaptive teams and<br>better employee experience"]
    style A fill:#ffebee,stroke:#C62828
    style B fill:#fff8e1,stroke:#F9A825
    style C fill:#e8eaf6,stroke:#5C6BC0
    style D fill:#e8f5e9,stroke:#388E3C
    style E fill:#e0f2f1,stroke:#00695C

flowchart TD
    A["Volatile business<br>environment"] --> C["Demand for<br>organizational agility"]
    B["Rising employee<br>expectations"] --> C
    C --> D["Agile HR:<br>iterative, co-created<br>people practices"]
    D --> E["Adaptive teams and<br>better employee experience"]
    style A fill:#ffebee,stroke:#C62828
    style B fill:#fff8e1,stroke:#F9A825
    style C fill:#e8eaf6,stroke:#5C6BC0
    style D fill:#e8f5e9,stroke:#388E3C
    style E fill:#e0f2f1,stroke:#00695C

Common Misconception: Agile HR Is Only for Technology Companies

Because agile methods originated in software, it is tempting to conclude that Agile HR belongs only in IT firms. The evidence points the other way. Banks such as ING, consumer goods firms, hospitals, and public sector bodies have applied agile ways of working to people practices, because the underlying conditions, shifting priorities and rising employee expectations, are industry-agnostic. What varies by industry is the appropriate degree and location of agility, a design question Chapter 13 takes up under agile organization design.

Implication for Your Study of This Subject

As you progress through this book, evaluate every practice you meet against two questions drawn from this chapter. First, which problem of the traditional model does this practice solve? Second, what feedback loop does it create, and how short is it? These two questions will let you distinguish substantive agility from what practitioners dismiss as “agile theatre”, the adoption of stand-ups and sticky notes without any change in how decisions are made.

1.5 Case Studies

1.5.1 Case Study 1: ING Bank, Reorganizing HR for an Agile Enterprise

In 2015, ING’s Netherlands headquarters dissolved its traditional departmental structure and reorganized around 350 nine-person squads grouped into thirteen tribes, borrowing deliberately from Spotify’s model (Denning, 2018). The people implications were immense. Nearly all headquarters employees had to reapply for positions in the new structure, and around thirty per cent ended up in different roles or left the organization. HR had to rebuild job architecture around squad roles such as chapter lead and product owner, redesign performance management to reward team delivery and knowledge sharing, and recruit for attitude and adaptability rather than narrow specialism. HR itself then adopted the same ways of working it was supporting, running people initiatives from backlogs with iterative delivery.

Discussion Questions:

Why did ING’s move to squads and tribes require re-selection of the workforce rather than a simple reporting-line change?
Which traditional HR artifacts, such as job descriptions or grade structures, would obstruct a squad-based organization, and why?
What risks accompany a transformation in which a third of employees change roles, and how should HR manage them?

1.5.2 Case Study 2: Adobe, Retiring the Annual Appraisal

Adobe abolished its annual performance review in 2012 after concluding that the ritual consumed tens of thousands of manager hours while demotivating employees, and that feedback delivered once a year arrived too late to improve anything. Its replacement, Check-In, is a lightweight rhythm of frequent conversations about expectations, feedback, and growth, with no ratings and no annual form. Managers received coaching in conversation quality rather than form-filling. Voluntary attrition fell in the years after the change, and the redesign is now cited widely as an early, influential example of iterating an HR product around user needs rather than administrative convenience (Dank & Hellström, 2020).

Discussion Questions:

Analyse Adobe’s decision using the agile value “responding to change over following a plan”. What was the plan, and what was the response?
What conditions would need to hold in an Indian IT services firm for a no-ratings model to work, given the industry’s tradition of bell-curve appraisal?
If frequent check-ins replace annual ratings, how should an organization now make promotion and pay decisions?

1.5.3 Case Study 3: Infosys, Continuous Feedback at Indian Scale

Indian IT majors followed a similar path in the mid-2010s. Infosys moved away from its bell-curve appraisal toward a continuous feedback approach supported by an internal digital platform, reflecting a broader industry shift as firms including Wipro and TCS re-examined forced ranking. The scale distinguishes the Indian cases: redesigning performance conversations for a workforce of hundreds of thousands, across delivery centres with strong hierarchical traditions, is a different order of challenge from a headquarters pilot. The lesson these cases add is that agile people practices must be localized, and that digital platforms, as Raines (2020) argues, are what make continuous practices feasible at enterprise scale.

Discussion Questions:

What implementation challenges does workforce scale add to a continuous feedback redesign?
How might strong hierarchical norms affect the honesty of frequent feedback conversations, and what could HR do about it?
Evaluate the claim that digital HR platforms are a precondition for Agile HR in large organizations.

1.6 Summary

Chapter Summary

Agile HR applies the values of the 2001 Agile Manifesto, iteration, collaboration, customer focus, and responsiveness to change, to the people function. It is best understood as the fourth phase in the historical evolution of people management, after personnel administration, human resource management, and strategic HRM, each of which solved its era’s problem and bequeathed rigidities to the next (Dank & Hellström, 2020). Two forces explain its emergence in the 2010s: business environments too volatile for annual, plan-driven people processes (Denning, 2018; Rigby, Elk, & Berez, 2020), and employees who expect their working experience to be designed with the care given to customers (Morgan, 2017; Whitter, 2019). Agile HR has two complementary faces, the HR function working agilely and HR redesigning its products for an agile organization, and cases from ING, Adobe, and Infosys show both in practice. Agility is a logic of short feedback loops, not a synonym for speed, and not the property of any single industry.

Key Terms

Agile Manifesto · Agile HR · Agile for HR / HR for Agile · Waterfall model · Iteration · Feedback loop · Personnel administration · Human resource management (HRM) · Strategic HRM · HR business partner · Squad and tribe · Continuous performance conversation · Agile theatre

Summary

Concept	Description
Agile Foundations
Agile Manifesto	A 2001 statement of four values and twelve principles for software development that later reshaped management practice
Agile values	Preferences for individuals, working outcomes, customer collaboration, and responsiveness over process, documentation, contract, and plan
Waterfall model	A sequential approach that fixes requirements up front and delivers results only at the end of a long cycle
Iteration	Delivering work in small pieces so that each piece can be tested and improved before the next
Feedback loop	The cycle by which the results of work return as information that shapes the next round of work
Defining Agile HR
Agile HR	The application of agile values, principles, and ways of working to the people function of an organization
Agile for HR	The HR function itself adopting agile ways of working such as backlogs, sprints, and experiments
HR for Agile	HR redesigning its products so that they support agile teams and an adaptive organization
Historical Evolution
Personnel administration	The early twentieth-century phase of transactional people management focused on payroll, discipline, and compliance
Human resource management	The 1980s phase that reframed people as resources and built standardized processes for selection, training, and appraisal
Strategic HRM	The 1990s phase that tied people practices to competitive strategy through planning and business partnering
Agile HR era	The phase from the mid-2010s in which HR adopted iterative, feedback-driven ways of working
Drivers and Evidence
VUCA environment	A volatile, uncertain, complex, and ambiguous business context that undermines long planning cycles
Employee expectation shift	The tendency of employees to judge work as an experience, raising the cost of rigid people processes
ING transformation	A 2015 reorganization of ING's headquarters into squads and tribes that required rebuilding core HR systems
Adobe Check-In	Adobe's 2012 replacement of annual ratings with frequent expectation and feedback conversations
Infosys continuous feedback	An Indian-scale move from bell-curve appraisal to platform-supported continuous feedback
Cautions
Agile theatre	The adoption of agile rituals and vocabulary without any change in how decisions are made
Speed misconception	The mistaken reading of agility as doing the same work faster rather than learning sooner