Executive Agile Transforming organizations with Agile leadership (Tomasz Manugiewicz)（Z-Library）

# Executive Agile: Transforming Organizations with Agile Leadership ## 【One-Line Pitch】 A practical guide for Agile coaches, transformation leaders, and aspiring executives who want to bridge the gap between Agile ways of working and C-level leadership, offering concrete frameworks for earning executive buy-in, coaching senior leaders, and orchestrating enterprise-wide change. ## 【Book Arc】 - **Opening (~0%–9%)**: Establishes the book's core premise—that Agile transformation fails without executive engagement—and introduces the CEO's role, accountabilities, and operating model as the foundation for understanding how to support enterprise change. - **Early (~9%–19%)**: Expands the executive landscape by mapping the expanding C-level roles (CFO, CTO, CPO, CHRO, COO), then addresses cognitive biases that block transformation, strategies for gaining executive buy-in, and the coaching skills needed to work effectively with senior leaders. - **Early (~19%–34%)**: Dives into the practical toolkit: understanding C-level expectations and needs, decoding different coaching approaches (from pure coaching to executive and team coaching), and building a clear vision with tangible results using frameworks like Dilts' logical levels. - **Middle (~34%–44%)**: Covers supporting CEOs directly—establishing coaching contracts, building authority and gravitas—then shifts to orchestrating Agile transformation using Lewin's change model and Kotter's 8-step framework. - **Middle (~44%–53%)**: Explores the mechanics of Agile software development (product backlogs, ceremonies, dependency management), building the Agile transformation team, selecting pilot teams, and introducing change using models like the Gartner hype cycle and Kübler-Ross change curve. - **Late (~53%–End)**: Concludes with personal career development, using Shirzad Shamine's Saboteurs model to help readers identify internal obstacles and create a stakeholder-informed career roadmap for Agile transformation leadership. ## 【Key Takeaways】 - **CEO time is the scarcest resource in any transformation** (Early): Understanding that a CEO's 1,440 daily minutes are limited means you must invest relationship-building time strategically—use advocates, prepare elevator pitches, and prioritize listening over talking when you do get access. - **The CEO's scope is the entire organization as one organism** (Middle): A CEO must understand knowledge domains ranging from product and engineering to legal, finance, and investor relations—but they can't be experts in all of them, which creates the gap Agile leaders can fill. - **Cognitive biases are transformation blockers that can be made conscious** (Early): Helping executives recognize their own biases—especially those common in Agile transformation contexts—is a concrete value-add that builds credibility and trust. - **Buy-in requires more than a good pitch—it requires trust and advocacy** (Early): Getting to the CEO's "inner cycle" depends on finding sponsors, mitigating executive concerns (cost, risk, trust), and demonstrating you understand their world before asking for anything. - **Coaching executives is different from coaching teams** (Early): Executive coaching requires establishing formal contracts, building authority and gravitas, and using models like McKinsey's Six Responsibilities of a CEO to identify where leaders actually need support. - **Change management models provide the scaffolding for Agile transformation** (Middle): Lewin's unfreeze-change-refreeze and Kotter's 8-step model (urgency, coalition, vision, communication, empowerment, quick wins, consolidation, institutionalization) give you a repeatable structure for introducing and sustaining change. - **Agile transformation starts with the right team and pilot selection** (Middle): Building an Agile community of practice, choosing pilot teams carefully, and transforming roles (Business Analysts to Product Owners, Project Managers to Scrum Masters) are foundational steps—and Conway's Law reminds us organizational design shapes product outcomes. - **Personal saboteurs, not just organizational barriers, hold back transformation leaders** (Late): Using Shamine's Saboteurs model (Judge, Avoider, Controller, Stickler, Restless, Hyper-achiever, etc.) helps you identify internal patterns that limit your career and effectiveness as a change agent. ## 【Reading Tips】 - **Skim Chapters 1–2 for the executive landscape overview** if you already work with C-level leaders; deep-read Chapter 4 (Getting Buy-in) and Chapter 8 (Supporting the CEOs) if relationship-building with executives is your primary challenge. - **Treat Chapter 9 (Orchestrating Agile Transformation) as the operational core**: Lewin and Kotter models are practical frameworks you can apply immediately—take notes on how to sequence quick wins and build coalitions. - **Chapter 10 (Agile Software Development) is foundational for non-technical readers** but may feel basic for experienced Agile practitioners—skim the ceremonies section and focus on dependency management at scale if you're already Agile-fluent. - **The career roadmap chapter (13) is best read as a self-reflection exercise** rather than a theoretical text—block time to work through the Saboteurs model honestly. - **Watch for the recurring "Flying Agility" case study** (introduced around the middle of the book) as a running example that ties concepts together—it helps ground abstract frameworks in a concrete scenario. ## 【Coverage Limits】 This guide synthesizes the book's structure, key frameworks, and practical takeaways from the available excerpts. Specific case study details, exercises, and deeper examples from later chapters (particularly the career roadmap and detailed coaching techniques) are not fully covered in the source material. ##