8: Agile Transformation, Change Management, and Scaling

Agile Project Management · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    8: Agile Transformation, Change Management, and Scaling

    Agile Transformation, Change Management, and Scaling

    Agile often begins with one team. A team adopts Scrum, visualizes work with Kanban, improves flow, runs retrospectives, and learns to deliver in smaller increments. But real organizations are far more complicated than a single team. Organizations have budgets, governance, approval processes, compliance needs, reporting structures, vendors, legacy systems, platform teams, executives, middle managers, departments, and competing priorities. A single team may become Agile while the larger organization continues to fund, measure, approve, and govern work in traditional ways, and this mismatch is precisely why Agile transformation is difficult.

    Agile transformation is not simply installing a framework, buying a tool, renaming project managers as Scrum Masters, or scheduling daily standups. It is a deeper change in how the organization thinks, decides, funds, measures, learns, and delivers value. A useful teaching phrase for this chapter captures that idea directly: Agile transformation is not installing a framework. It is changing how the organization learns.

    This chapter moves from team-level Agile to organizational agility. It explains how organizations move from current state to future state, why change management matters, how Kotter's 8-Step Change Model can support Agile adoption, how teams choose the right way of working, and how scaling frameworks help multiple teams coordinate delivery across an entire organization.

    Learning Objectives

    By the end of this chapter, you should be able to:

    • Explain why Agile transformation is cultural change, not just process change.
    • Describe how to move from current state to future state using a change framework.
    • Explain Kotter's 8-Step Change Model in the context of Agile adoption.
    • Choose an appropriate way of working based on work type, uncertainty, governance, and scale.
    • Explain how governance, funding, compliance, and organizational alignment affect Agile delivery.
    • Describe major scaling approaches such as Scrum of Scrums, Nexus, LeSS, SAFe, and Disciplined Agile.
    • Recognize common Agile transformation anti-patterns.
    • Identify PMI-ACP traps related to transformation, scaling, governance, and organizational change.


    This page titled 8: Agile Transformation, Change Management, and Scaling was last modified on Mon, 31 Aug 2026 12:00:10 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.