What's New in the Agile Practice Guide – Second Edition

When PMI and Agile Alliance published the first edition of the Agile Practice Guide in 2017, agile approaches were already in wide use beyond software. Engineering, marketing, and education teams had adopted them, and the guide recognized that reach from the start.

What has changed in the nine years since is not where agile is used but how it is practiced. Teams are frequently distributed across cities and time zones, generative AI has joined our planning sessions, and product thinking shapes how work is framed and measured.

The Agile Practice Guide – Second Edition updates this widely used, framework-neutral introduction to agile so it reflects how practitioners work today. It still begins with the individual and the team, while acknowledging the scaled and enterprise settings that now surround them.

A guide built from how practitioners work

The guide has always been grounded in evidence rather than opinion. Its content draws on surveys of PMI and Agile Alliance members. Practitioners were asked how they apply agile approaches day to day and what they would want new team members to understand. Job task analysis involving thousands of practitioners shaped what made it into the guide and what stayed out.

That evidence base drove a deliberate design decision that carries into the second edition: the guide stays neutral across frameworks. Iterations are not always called sprints, facilitators are not all called scrum masters, and no single approach is endorsed over another. The goal was, and remains, a practical guide for people new to agile who want a trustworthy footing before they choose a direction.

Why a second edition now

The first edition arrived before the pandemic reshaped how teams work. Remote and hybrid arrangements are now more common, even as some organizations call people back to the office, and that push and pull continues to shape team dynamics. Generative AI has arrived as a genuine collaborator in planning, writing, and analysis, though it also brings real risks of error and bias alongside its benefits.

Practitioners increasingly pair agile approaches with adjacent disciplines such as customer-centric design, and rapid market validation. Scaling frameworks, once considered specialized, are now in routine use across large organizations.

The pressure behind these shifts is measurable. In recent PMI research, 81% of project professionals report that their projects are becoming more complex, and 61% report losing value to that complexity. Organizations pursuing agile transformation face the same squeeze from the top, since executives must keep rethinking operating models built for a slower changing era. The second edition responds to this environment with updated guidance, current terminology, and practical tools for the teams doing the work.

What changed in the second edition

The guide organizes its updates into three groups:

Practice changes. The binary label of "hybrid" gives way to a delivery continuum, that better reflects reality and invites teams to select the mix of predictive and agile practices that fit each situation. Terminology has been modernized: backlog grooming is now backlog refinement, and daily standups have become daily coordination meetings. Product management thinking is deeply integrated, which is covered in its own section below. Every chapter now closes with GenAI insights, offering ideas on where AI could help and cautions on where it could harm without caution.

Social changes. Psychological safety is treated as a baseline requirement for team performance rather than a nice-to-have. People do their best work when they feel safe to raise concerns and share new ideas. Sustainability has grown beyond the original call for a sustainable pace into decisions that safeguard people, the planet, and long-term prosperity. More inclusive language runs throughout, reflecting a broader cultural shift in how team members relate to one another.

Strategic changes. The guide acknowledges that scaling frameworks such as SAFe®, LeSS, Scrum@Scale, and Disciplined Agile® are now widely adopted, and it explains when and how to think about them. It also introduces enterprise agility as the organizational context many teams now operate within, pointing readers toward the Manifesto for Enterprise Agility and the M.O.R.E. principles from the PMBOK® Guide – Eighth Edition for those who want to go deeper.

Still a practical starting point for learning agile

For all that is new in this edition, the guide's core purpose is unchanged. It explains what agile is, why it suits high-uncertainty work, and how to get started, first as an individual and then as a team. The broader material on scaling and organizational agility builds outward from this core foundation.

Readers new to agile will find guidance on selecting a development life cycle and chartering a project and a team. They will also find practical coverage of scope refinement sessions, retrospectives, and delivering value in small, frequent increments. The measurement guidance has been substantially expanded, moving past output counts toward agile metrics that capture flow, outcomes, and value more directly.

Flow metrics, Goal Question Metric thinking, and objectives and key results (OKRs) all receive practical treatment, with common pitfalls called out. For PMI Agile Certified Practitioner (PMI-ACP)® candidates and credential holders, the guide remains a natural companion for keeping agile knowledge current.

Agile meets product management

The largest single expansion in the second edition reflects something our practitioner research surfaced clearly: the rise of product management thinking. Teams increasingly own products continuously rather than delivering a project and disbanding, and their working vocabulary has been aligned to match this.

The guide incorporates agile-adjacent approaches that teams commonly use alongside agile delivery. These are complementary disciplines with their own origins, not agile methods, and the guide is careful to keep that distinction. Design thinking brings customer-centric development to the front end of work, using empathy and low-fidelity prototypes to invite rapid feedback while change is still cheap. Lean Startup treats every new idea as a testable hypothesis, using minimum viable products, A/B testing, and build-measure-learn loops to validate direction, and to pivot before further money is spent.

It also covers go-to-market considerations, product life cycle phases, and how product management operates as both a function and a role alongside project responsibilities. It introduces these concepts, shows how teams combine them thoughtfully, and points to deeper resources for readers who want more.

Where agile fits in the bigger picture

Some readers will come to the guide from the organizational side. In a healthy agile organization, teams tailor their practices to their own context, and that autonomy builds the ownership and accountability that make agile work.

The challenge for leaders is not standardizing those teams but coordinating them: sharing a common vocabulary, connecting team-level work to strategy, and making delivered value visible to sponsors.

PMI research suggests the appetite for this outpaces the follow-through. Some 85% of C-suite executives recognize enterprise agility as critical, yet 65% have implemented it only to a limited extent or not at all.

The guide helps here as a shared, framework-neutral reference rather than as a transformation manual. Its organizational chapter covers culture assessment, team structures, business practices that enable agility, lean portfolio management, and the evolving role of an agile PMO.

The guide does not try to be a scaling handbook; it tells you these approaches exist, what problems they address, and where to learn more. Organizational change management, a discipline in its own right, is explicitly signposted to PMI's dedicated practice guide on that subject.

A guide that evolved with the practice.

The Agile Practice Guide – Second Edition reflects how agile practice has genuinely evolved. Adoption across industries has deepened, teams are more distributed, product thinking is mainstream, and awareness of the organizational settings around the work has grown.

Through all of that, it keeps its original promise as a practical, evidence-based, framework-neutral introduction for anyone starting or refreshing their agile journey. Read it to understand the fundamentals, use it to choose approaches that fit your context, and follow its signposts when you are ready to explore scaling and enterprise agility further.

Tags: Agile | Product Management | PMO | Transformation | Artificial Intelligence

Related Insights

You May Also Like