Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Agile HR

Agile HR

Deliver Value in a Changing World of Work
Help HR solve workforce problems faster, with experiments that reveal which changes actually work.
by Natal Dank 2020 328 pages
4.25
80 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Make HR prove value in the employee’s work, not the paperwork it produces

Measure what matters. Agile HR applies Agile thinking to people operations: define who the work serves, identify the value it should create, and test whether that value is real. Employees are HR’s immediate customers, while the organization’s customers also matter because people practices affect service and business results.

A costly ritual exposed. Natal Dank describes a bank process that spent almost six months sorting staff into 25 talent categories and generating executive reports. The information rarely shaped promotions or development, and managers avoided discussing it with employees. Agile HR starts from a different question: does this process help people do better work? It replaces inherited procedure with collaborative, evidence-informed service design.

Analysis

The shift from activity to value is a useful corrective to the familiar institutional habit of treating completed forms as proof of impact. It also connects HR to service design, where success depends on whether a service solves a user’s problem, not whether its provider followed a procedure. Still, value is not self-evident: employee preference, business outcomes, fairness, and legal obligations can conflict. Making those trade-offs explicit is more credible than claiming every initiative benefits everyone equally.

Use Agile when uncertainty is high, and retain waterfall for predictable work

Match method to conditions. Waterfall plans the scope, schedule, budget, and sequence before work begins. It remains useful when requirements are stable and repeatable, such as processing a statutory pay adjustment or organizing a familiar event. Agile is better suited to work where needs or conditions are likely to change, and the answer cannot be known in advance.

Plans meet reality. A complex culture or performance initiative may involve many stakeholders, changing business priorities, and users who only discover what they need once they try a solution. Detailed upfront plans can then create expensive rework. Agile instead uses short cycles of planning, action, review, and adjustment. The pandemic examples in the book show the value of reprioritizing quickly, including launching employee support services in days and improving them incrementally.

Analysis

This is strongest when Agile is treated as a response to uncertainty, not a synonym for speed or modernity. Project-management research often distinguishes predictable work from complex work, where cause and effect become clear only after action. Yet many organizations contain both conditions at once. Payroll may need strict repeatability, while the employee experience around pay needs experimentation. The practical challenge is not choosing one ideology, but separating stable requirements from uncertain design questions.

Study the employee’s lived journey before choosing a solution

Investigate before prescribing. Design thinking is a human-centered method for understanding users, defining a problem, generating ideas, and testing possible solutions. In HR, it can prevent a familiar mistake: designing a grand program around an assumption rather than a demonstrated need.

A small fix beat a redesign. One team planned to rebuild its graduate program after noticing that many accepted candidates failed to arrive. Interviews and testing revealed that graduates mainly needed to feel welcomed and wanted. A simple call from their future manager before their start date addressed the issue, avoiding a large redesign. In the book’s onboarding example, interviews, observation, personas, and journey maps help reveal distinct needs across new hires and existing staff. The aim is to find the moments that matter, not to produce elaborate research for its own sake.

Analysis

Journey research makes invisible friction visible. A new hire’s experience crosses HR, IT, facilities, managers, and teammates, so a problem that appears to belong to one function may actually emerge from handoffs between them. This aligns with human-factors research, which studies how people interact with whole systems rather than isolated tools. Personas can help teams notice varied needs, but they are hypotheses, not facts about individuals. They should be checked with real people and revised when evidence contradicts the template.

Make the HR wish list compete for value, capacity, and attention

Define value broadly. The book identifies several lenses for HR priorities: strategic value to business goals, enabling value that removes friction, purpose and social value, employee value, and value to the organization’s end-customer. A people initiative can serve several of these at once, but its contribution should be made clear.

Choose what fits. HR can build a portfolio from business priorities, people data, market conditions, and employee feedback, then rank work with tools such as an effort-impact grid or MoSCoW, which sorts needs into must-have, should-have, could-have, and not-now. The authors recommend planning around roughly 70 percent of team capacity, leaving room for unexpected work and time away. A visible portfolio also makes it easier to explain what will wait when an urgent request arrives.

Analysis

A portfolio makes scarcity discussable. Rather than pretending every worthy initiative can happen now, HR can show which choices support which outcomes and what is being deferred. This resembles portfolio management in finance, where a collection is judged by risk and return rather than by the appeal of each item alone. The framework also needs a safeguard: easily measured short-term gains can crowd out harder-to-quantify goals, such as inclusion or long-term capability. Explicit value criteria make that bias easier to challenge.

Test cheap prototypes before a polished rollout

Learn before investing. A prototype is a quick, inexpensive version of a possible service or product that lets users react to something tangible. An MVP, or minimum viable product, contains just enough to test whether the idea works. A minimum lovable product describes a version improved through user feedback so that people find it genuinely useful.

A failed app found the real problem. An HR team assumed a technology company would welcome an app for peer feedback. Employees disliked the tool. What they wanted was a safe setting for honest discussion without ratings and bonus figures dominating the conversation. Because the team tested first, it could stop the app experiment and investigate the actual need. A pilot can become an expensive near-final rollout; an experiment should be small enough that negative results can change the decision.

Analysis

Prototypes lower the social and financial cost of being wrong. They also make disagreement concrete: people can respond to a mock-up or an experience instead of debating an abstract proposal. This is a form of organizational learning, because the test changes what the team knows before it commits resources. But experimentation is not automatically rigorous. A handful of enthusiastic volunteers may not represent the workforce, and a test can expose sensitive information. Clear hypotheses, diverse participants, and ethical safeguards matter.

Choose Scrum for bounded innovation, Kanban for continuous HR work

Fit the workflow. Scrum organizes product development into timeboxed periods called sprints. Its roles include the development team, a product owner who prioritizes what to deliver, and a Scrum master who helps the team improve and remove obstacles. Sprint reviews gather feedback on the work, while retrospectives examine how the team worked.

Keep ongoing work moving. Kanban visualizes work on a board and limits how many items are in progress, helping teams finish work before taking on more. Scrum can suit a defined project, such as designing a new learning service. Kanban often fits continuous work such as recruitment or HR operations. Both rely on visible priorities, realistic capacity, and clear completion criteria. Scrum is not a checklist of meetings, and Kanban is not merely a board: each should change how work is selected and managed.

Analysis

The distinction is practical: Scrum creates a rhythm for focused development, while Kanban makes ongoing demand and bottlenecks visible. Limiting work in progress also counters the illusion that starting many tasks means making faster progress. In cognitive terms, frequent switching carries coordination costs, though the book does not quantify them for HR. Neither framework can fix an overloaded or under-resourced team by itself. A board that makes excess demand visible is valuable only if leaders can act on what it reveals.

Use evidence to challenge HR fashion, senior opinion, and false causality

Treat decisions as hypotheses. Evidence-based practice combines professional experience with people and business data, stakeholder perspectives, and credible research. HR teams should state what they expect to happen, decide how to measure it, and look for evidence that could disprove their idea. A correlation between engagement scores and financial performance, for example, does not by itself show that one caused the other.

Tie people data to outcomes. In a MUJI recruitment project, an Agile team used automation and supportive candidate communications to cut the early recruitment step from one to two months to two to three days. The company hired nearly 100 people on time at less than half the cost of an agency. The authors also recommend control groups, attention to privacy, and partnerships with data specialists when appropriate.

Analysis

The scientific stance protects HR from both executive intuition and fashionable interventions. It also demands intellectual humility: a result may reflect selection effects, timing, or other changes rather than the program under review. The book’s cases illustrate useful measurement, but many are reported as organizational examples rather than controlled causal studies. That makes them practical prompts, not universal proof. Strong HR analytics pairs quantitative indicators with context, checks who is missing from the data, and treats prediction as decision support rather than an automatic verdict about people.

Replace HR silos with teams accountable for whole employee journeys

Connect the specialties. The traditional Ulrich-style HR structure separates business partners, specialist centers, and shared services. The book argues that this can create handoffs: specialists design in isolation, business partners carry solutions into the organization, and service teams hear user complaints without the authority to redesign the process.

Organize around the experience. Agile HR brings different skills together in cross-functional teams and may include people from IT, finance, communications, or the business itself. Some teams manage routine work through Kanban while forming short-lived squads for strategic projects. More developed models organize around employee groups or journeys, such as onboarding or career development. The aim is end-to-end accountability, not simply a new name for HR. Different operating models are options to test, not templates to copy.

Analysis

This design echoes product teams that own a service from discovery through maintenance. It can reduce the distance between the people designing a policy and those experiencing its consequences. The trade-off is that broad accountability requires enough generalist capability, clear decision rights, and coordination across teams. Specialist knowledge still matters, particularly in compensation, employment law, and data privacy. The aim is not to abolish expertise, but to make expertise collaborate around an outcome instead of treating departmental boundaries as the customer’s problem.

Transform the operating system, not just install Agile ceremonies

Start with a reason. Organizations adopt Agile for different pressures, including digital change, faster product development, growth, or redesigning customer-facing services. HR should help leaders and employees explain why the change fits their situation, then evolve it through experiments rather than imposing a universal model.

Change the conditions too. A team cannot self-organize if managers continue assigning competing work, approval chains block decisions, or performance systems reward individual competition. Transformation may involve pilots and a period of mixed Agile and traditional practices. The book describes scaling options such as SAFe, Scrum at Scale, Spotify’s squads, and LeSS, but cautions that these are not ready-made blueprints. Teams should first demonstrate a useful way of working; then the organization can adapt structures, roles, policies, and leadership practices to support it.

Analysis

Ceremonies are visible, so organizations can adopt them while leaving the underlying authority structure untouched. That produces the appearance of change without transferring meaningful decision rights. Organizational research often describes this gap as decoupling formal structures from everyday practice. The book’s insistence on context and leadership behavior addresses that risk. At the same time, gradual transformation can become an excuse for indefinite ambiguity. Clear mandates, explicit responsibilities, and forums for resolving conflicts help experimentation proceed without making employees guess which system governs their work.

Redesign performance and reward around timely learning and collaboration

Question the annual ritual. The book describes traditional reviews as time-consuming, backward-looking, and often linked to ratings and individual bonuses that can undermine teamwork. It recommends testing more frequent feedback, adaptive goals, peer input, and separate conversations about development and pay.

One trial showed promise. At Sky Betting and Gaming, a 12-month experiment with about 120 technology employees removed ratings and separated individual performance from bonuses. It introduced regular conversations, peer-reviewed management decisions, learning resources, and transparent team recognition. In that group, 92 percent said they knew what was expected of them, 87 percent reported receiving relevant feedback, and the employee net promoter score rose from 36 to 55. These are encouraging results from one organizational test, not proof that the same design will work everywhere.

Analysis

Performance systems do more than record performance: they signal which behaviors the organization rewards. Individual incentives can conflict with interdependent work, while continuous feedback can shorten the distance between action and learning. The Sky example is compelling precisely because it combines changes rather than testing one isolated element, which also makes causal attribution difficult. Fairness, pay decisions, and underperformance still require accountable processes. Removing a rating is not the same as removing judgment; it shifts the burden toward better evidence, conversation, and manager capability.

Grow talent through real work and skill networks, not static labels

Let capability emerge. Agile HR questions fixed talent categories, narrow high-potential lists, and career ladders built around hierarchy. Roles and needed skills can change quickly, so organizations should create chances for people to learn through projects, mentoring, peer networks, and work that stretches their abilities.

Make development accessible. The book highlights on-demand learning, team or individual learning budgets, social learning, fluid career moves, and transparent internal talent pools. These practices can help people build broader, T-shaped skills: range across different kinds of work, combined with depth in a specialty. They also make development part of work rather than a separate annual event. The point is not that formal training or succession planning is useless, but that neither should be the only route for recognizing and growing capability.

Analysis

This view treats talent as something shaped by opportunity, not merely discovered by assessment. It aligns with learning theories that emphasize practice, feedback, and progressively harder tasks. Internal markets and flexible assignments can also help organizations use skills they already possess. However, open access alone does not guarantee fairness: visibility, manager sponsorship, and time to participate may be distributed unevenly. Without monitoring who gets developmental opportunities, a fluid system can reproduce old advantages under a more informal label.

Schedule reflection and improvement, or urgent delivery will crowd them out

Turn learning into work. A retrospective is a structured team review of what happened, what helped or hindered progress, and which changes to try next. Its purpose is improvement, not blame. The book advises making improvement tasks visible in the team backlog, because insight alone does not guarantee action. HR can also use regular employee feedback, service reviews, and combined data sources to keep learning about the employee experience.

Start small and protected. Tracey Waters’s team tried Agile for 90 days, then adapted its approach when sprint work competed with routine responsibilities. During the pandemic, Agile HR teams used short cycles to set up employee helplines and leader support rapidly. The lesson is to begin with a meaningful problem, a timeboxed experiment, protected team capacity, and a safe way to discuss both failure and success.

Analysis

Reflection is productive only when teams have permission and resources to act on what they learn. This connects to organizational learning: groups need both feedback and a mechanism for changing routines in response. Psychological safety helps people surface problems, but it is not a substitute for accountability or follow-through. A useful test is whether the next cycle looks different because of the previous review. If the same blockers recur without an owner or decision path, the retrospective has become another meeting rather than an improvement system.

Analysis

Agile HR is best understood as a redesign of how an organization learns about people-related work. The book’s central move is to replace HR’s traditional sequence of design, approval, rollout, and attempted adoption with a loop: identify a consequential problem, learn from the people experiencing it, test a small intervention, measure results, and adapt. This reframes HR from a policy factory into a service and organizational-design partner.

The strongest argument is not that every process should become flexible. It is that the method should fit the degree of uncertainty. Stable, legally constrained transactions need consistency; poorly understood cultural or behavioral problems need discovery and experimentation. That distinction protects Agile from becoming a fashionable label and makes room for governance, compliance, and employee rights.

The book also makes a systemic claim: team practices cannot thrive when incentives, reporting lines, budgets, and management authority continue to reward the old behavior. A backlog does little if executives can bypass it with unprioritized demands. Self-organization needs a shared purpose, transparent information, decision authority, and a route for escalating impediments. Those are organizational conditions, not meeting techniques.

Its evidence should be read with appropriate restraint. Case studies show plausible mechanisms and practical results, but reported outcomes often come from single organizations, bundled interventions, or before-and-after comparisons. The Sky performance experiment, for instance, gives a promising signal without isolating which feature caused the change. The book’s own scientific standard therefore suggests a disciplined conclusion: adapt the examples, test them locally, and avoid treating success elsewhere as proof.

The most durable contribution is a professional stance. HR can be both humane and commercially rigorous by measuring effects on employees and customers, questioning practices that create administrative burden, and making trade-offs visible. Agility is not speed at any cost. It is the capacity to learn and change without losing responsibility for people.

Summary in 30 Seconds
Use flexible, short cycles for uncertain people problems, while keeping stable, regulated work predictable. Begin with employees’ needs, test small interventions, measure outcomes, and change course when evidence contradicts assumptions. Reserve about 30 percent of team capacity for unexpected work. One recruitment project cut an early hiring stage from one or two months to two or three days, hiring nearly 100 people at less than half the agency cost. Durable change also requires aligned authority, incentives, and team structures.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.25 out of 5
Average of 80 ratings from Goodreads and Amazon.

Agile HR receives high praise from readers, with an average rating of 4.24 out of 5. Reviewers appreciate its practical approach, clear explanations, and abundance of examples and tools. The book is lauded for its comprehensive coverage of Agile principles in HR, offering valuable insights for professionals looking to transform their practices. Readers find it inspiring and easy to digest, highlighting its usefulness as a guide for implementing Agile methodologies in HR. Many consider it a must-read for HR professionals seeking to move beyond traditional models and create more value in their organizations.

Your rating:
4.59
172 ratings
Want to read the full book?

Glossary

Agile HR

Adaptive, value-focused people operations

An application of Agile values and working methods to human resources and people operations. Agile HR prioritizes work by the value it creates for employees, the business, and end-customers; develops services incrementally; and uses feedback, experimentation, and evidence to adapt. It includes both improving how HR teams work and helping organizations redesign people practices for greater adaptability.

Design thinking

Human-centered problem exploration

A set of methods for understanding users and developing solutions around their needs. The process commonly involves investigating a business challenge, empathizing with users, identifying patterns, defining a problem, generating ideas, making prototypes, and testing them. The steps can loop back as new evidence changes the team’s understanding.

Minimum viable product (MVP)

Smallest useful test version

A version of a product or service with only the features needed to test whether an idea works for users. In Agile HR, an MVP might be a basic feedback tool or a rough onboarding experience. It is released or tested early so that evidence can guide further investment, rather than assuming a complete design is needed before learning begins.

Minimum lovable product (MLP)

Tested, appealing product version

A product or service developed from an initial test version by using real user reactions to improve its usefulness and appeal. The term emphasizes that the goal is not merely to make something technically functional, but to learn what people value and refine the experience accordingly.

Product backlog

Prioritized work inventory

A changing, prioritized list of work that may be needed to develop or improve a product, service, or initiative. The backlog reflects what the team currently knows, with the most valuable work placed first. Teams regularly revise it as priorities, user feedback, capacity, and evidence change.

Definition of Done (DoD)

Shared completion standard

A set of shared requirements that every completed piece of work must satisfy. It can include quality, testing, compliance, brand, and user-validation standards. The Definition of Done applies across a product or project, while acceptance criteria specify the requirements for an individual backlog item.

Scrum

Timeboxed product-development framework

An Agile framework in which a team works in consecutive, time-limited sprints to produce reviewable increments of value. Scrum defines a development team, a product owner responsible for priorities, and a Scrum master who supports the framework and helps remove obstacles. Planning, daily coordination, review, and retrospective events create a recurring learning cycle.

Kanban

Visual continuous-flow method

A method for making work visible, limiting the amount in progress, and improving how tasks move from start to completion. A Kanban board shows the state of work, often through columns such as backlog, to do, doing, and done. It is especially useful for continuous work, including HR operations and services.

T-shaped teams

Broad skills plus deep expertise

Teams whose members combine knowledge across several areas with depth in particular specialties. This mix allows the team to collaborate on end-to-end problems while drawing on expert capability when needed. The book contrasts this approach with narrow functional silos in which work depends on repeated handoffs between specialists.

Agile-by-nature

Agile values from inception

An organization that has developed around Agile principles such as trust, transparency, self-management, and customer focus from its beginning, rather than transforming from a traditional hierarchy. As these organizations grow, their challenge is to add enough coordination and structure to scale without replacing their adaptive culture with unnecessary bureaucracy.

Objective key results (OKRs)

Objectives with measurable results

A goal-setting approach in which individuals or teams define objectives and a small set of measurable key results that indicate progress. OKRs are shared transparently and aligned with broader organizational aims. In the book’s account, they can support adaptive performance conversations, while remaining separate from automatic links to individual bonuses.

FAQ

What's Agile HR: Deliver Value in a Changing World of Work about?

  • Agile Mindset in HR: The book focuses on adopting an Agile mindset within HR to enhance organizational effectiveness, translating Agile principles from software development into HR practices.
  • Value Delivery: It emphasizes prioritizing work based on the value delivered to employees and end-customers, encouraging HR to act as a strategic, value-adding function.
  • Co-Creation and Collaboration: The book highlights the importance of co-creating HR solutions with employees and stakeholders to ensure they meet real user needs.

Why should I read Agile HR?

  • Transformative Insights: The book offers practical insights and tools for HR professionals to modernize their practices and embrace Agile methodologies.
  • Real-World Applications: It includes case studies and examples illustrating how Agile HR principles can be applied in various organizational contexts.
  • Empowerment of HR Teams: Readers can learn how to empower HR teams to deliver better employee experiences and drive organizational success through Agile practices.

What are the key takeaways of Agile HR?

  • Agile Mindset is Essential: Adopting an Agile mindset is crucial for HR to thrive in a complex and rapidly changing business environment.
  • Customer-Centric Approach: HR should place the internal customer (employees) at the heart of all initiatives to enhance the employee experience.
  • Continuous Improvement: The book advocates for a culture of continuous improvement within HR, where teams regularly assess and adapt their practices.

What is the Agile mindset, and how does it apply to HR?

  • Core Principles: The Agile mindset centers around delivering value, embracing change, and fostering collaboration, prioritizing employee needs in HR.
  • Incremental Development: Agile HR promotes an incremental approach to developing HR solutions, allowing for testing and validation before full implementation.
  • Data-Driven Decisions: HR professionals are encouraged to use data and evidence to inform decisions and improve processes, demonstrating their impact on success.

How does Agile HR define value in HR practices?

  • Multiple Dimensions of Value: The book outlines strategic, enabler, purpose-driven, employee, and end-customer value to assess HR initiatives' impact.
  • Strategic Alignment: Value is defined by how HR practices align with business strategy and contribute to competitive advantage.
  • Employee Experience Focus: Enhancing the employee experience is a key component of value, aiming to create a positive work environment.

What is the Agile HR toolkit mentioned in Agile HR?

  • Practical Framework: The toolkit consists of tools and techniques for implementing Agile practices effectively in HR.
  • Step-by-Step Guidance: It provides step-by-step guidance on applying Agile principles in HR contexts.
  • Focus on Collaboration: The toolkit encourages collaboration between HR and other business functions for co-created solutions.

How does Agile HR suggest HR teams can co-create solutions?

  • Engagement with Stakeholders: The book advocates involving employees and stakeholders in designing HR products and services.
  • Design Thinking Techniques: HR teams are encouraged to use design thinking methodologies to empathize, define, ideate, and prototype.
  • Iterative Feedback Loops: Establishing feedback loops allows users to provide input on prototypes, refining offerings based on real-world experiences.

What are Scrum and Kanban, and how do they relate to Agile HR?

  • Scrum Framework: Scrum emphasizes iterative development through timeboxed sprints, helping HR teams manage projects effectively.
  • Kanban Method: Kanban focuses on visualizing work and managing flow to optimize efficiency, allowing HR teams to handle tasks based on capacity.
  • Application in HR: Both frameworks can be adapted for HR, improving processes, enhancing collaboration, and delivering better employee experiences.

How can HR teams implement continuous improvement practices according to Agile HR?

  • Regular Retrospectives: Conducting retrospectives helps assess team performance and identify areas for improvement.
  • Feedback Mechanisms: Establishing mechanisms for gathering feedback from employees and stakeholders informs adjustments to HR practices.
  • Iterative Approach: Continuous improvement involves regularly reviewing and refining processes based on feedback and performance metrics.

What are the challenges of Agile transformation mentioned in Agile HR?

  • Resistance to Change: Employees may resist Agile transformation due to fear or lack of understanding, requiring education and communication.
  • Balancing Structure and Flexibility: Organizations struggle to balance necessary structures with flexibility, affecting Agile practices' effectiveness.
  • Cultural Shift: Transforming to an Agile mindset requires a significant cultural shift, with HR playing a crucial role in facilitating change.

How does Agile HR define performance management in an Agile context?

  • Continuous Feedback: Performance management should focus on continuous feedback rather than annual reviews for real-time adjustments.
  • Team-Based Goals: Shared objectives promote collaboration among team members, aligning with Agile principles.
  • Decoupling Rewards from Ratings: Separating performance ratings from rewards reduces competition and encourages teamwork.

What are the best quotes from Agile HR and what do they mean?

  • Facilitators of Success: "HR need to be the facilitators of success, not the dictators of best practice," emphasizes adaptability in HR practices.
  • Agile Journey: "Once you start on an Agile journey you never go back," reflects the transformative nature of adopting Agile practices.
  • Growing Movement: "The Agile HR movement has been growing organically for some years now," indicates a shift towards dynamic HR practices.

About the Author

Natal Dank is a pioneering figure in the field of Agile HR. As the author of "Agile HR," she demonstrates extensive experience and insight into applying Agile methodologies within human resources. Dank's work is characterized by its practical, hands-on approach, providing readers with actionable tools and strategies. Her writing style is clear and engaging, making complex concepts accessible to a wide audience. Dank's expertise in Agile HR positions her as a thought leader in the industry, offering innovative solutions to modernize HR practices. Her book reflects a deep understanding of both Agile principles and HR challenges, bridging the gap between these two domains effectively.

Download PDF

To save this Agile HR summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.39 MB     Pages: 23

Download EPUB

To read this Agile HR summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.33 MB     Pages: 29
Want to read the full book?
Follow
Listen13 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...