Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation

Book description

Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation: An Action Guide for Business and IT Leaders explains how to increase IT delivery capabilities through the use of Agile and Kanban. Factoring in constant change, communication, a sense of urgency, clear and measurable goals, political realities, and infrastructure needs, it covers all the ingredients required for success.

Using real-world examples, this practical guide illustrates how to implement Agile and Kanban in software project management and development across the entire IT department. To make things easier for busy IT leaders and executives, the text includes two case studies along with numerous templates to facilitate understanding and kick-start implementation.

Explaining how IT and business management can work together to determine business goals that drive this IT-wide undertaking, the book arms you with actionable solutions that can be put to use immediately in any IT department, regardless of size.

Table of contents

  1. Front Cover (1/2)
  2. Front Cover (2/2)
  3. Contents (1/2)
  4. Contents (2/2)
  5. Foreword
  6. Foreword
  7. Preface: What Is This Book About?
  8. Acknowledgments
  9. About the Authors
  10. Chapter 1 - Ineffectiveness of IT Software Project Management and Development: What Can We Do about It?
  11. Chapter 2 - Executive Summary of Agile (Scrum) and Kanban (Lean) (1/4)
  12. Chapter 2 - Executive Summary of Agile (Scrum) and Kanban (Lean) (2/4)
  13. Chapter 2 - Executive Summary of Agile (Scrum) and Kanban (Lean) (3/4)
  14. Chapter 2 - Executive Summary of Agile (Scrum) and Kanban (Lean) (4/4)
  15. Chapter 3 - Why Agile Alone May Not Be Enough or the Right Solution, and Why Implementing Agile or Kanban without Good Business Objectives Will Normally Fail (1/4)
  16. Chapter 3 - Why Agile Alone May Not Be Enough or the Right Solution, and Why Implementing Agile or Kanban without Good Business Objectives Will Normally Fail (2/4)
  17. Chapter 3 - Why Agile Alone May Not Be Enough or the Right Solution, and Why Implementing Agile or Kanban without Good Business Objectives Will Normally Fail (3/4)
  18. Chapter 3 - Why Agile Alone May Not Be Enough or the Right Solution, and Why Implementing Agile or Kanban without Good Business Objectives Will Normally Fail (4/4)
  19. Chapter 4 - Seven-­Step Software Delivery Improvement Framework (1/2)
  20. Chapter 4 - Seven-­Step Software Delivery Improvement Framework (2/2)
  21. Chapter 5 - Step 1: Identify the (Business) Sponsor and Her or His Needs and Goals
  22. Chapter 6 - Step 2: Perform Environment Boundary Identification and Assessment (1/2)
  23. Chapter 6 - Step 2: Perform Environment Boundary Identification and Assessment (2/2)
  24. Chapter 7 - Step 3: Envision Scenarios and Risks (1/2)
  25. Chapter 7 - Step 3: Envision Scenarios and Risks (2/2)
  26. Chapter 8 - Step 4: Detail the Chosen Action Plan (1/2)
  27. Chapter 8 - Step 4: Detail the Chosen Action Plan (2/2)
  28. Chapter 9 - Step 5: Implement the Chosen Action Plan
  29. Chapter 10 - Step 6: Inspecting the Implementation’s Progress (1/2)
  30. Chapter 10 - Step 6: Inspecting the Implementation’s Progress (2/2)
  31. Chapter 11 - Step 7: Adapt the Chosen Action Plan (as Needed) (1/2)
  32. Chapter 11 - Step 7: Adapt the Chosen Action Plan (as Needed) (2/2)
  33. Chapter 12 - Lessons Learned
  34. Case Study 1: “Customized Agile Combined with Kanban” (1/7)
  35. Case Study 1: “Customized Agile Combined with Kanban” (2/7)
  36. Case Study 1: “Customized Agile Combined with Kanban” (3/7)
  37. Case Study 1: “Customized Agile Combined with Kanban” (4/7)
  38. Case Study 1: “Customized Agile Combined with Kanban” (5/7)
  39. Case Study 1: “Customized Agile Combined with Kanban” (6/7)
  40. Case Study 1: “Customized Agile Combined with Kanban” (7/7)
  41. Case Study 2: “(Customized) Agile and Kanban Coexistence” (1/5)
  42. Case Study 2: “(Customized) Agile and Kanban Coexistence” (2/5)
  43. Case Study 2: “(Customized) Agile and Kanban Coexistence” (3/5)
  44. Case Study 2: “(Customized) Agile and Kanban Coexistence” (4/5)
  45. Case Study 2: “(Customized) Agile and Kanban Coexistence” (5/5)
  46. Appendix A: From the Project Management Office to the Project Delivery Office
  47. Appendix B: Change Management
  48. Appendix C: Two Most Important Tools of a Good Software Development Infrastructure
  49. Glossary
  50. Bibliography
  51. Back Cover

Product information

  • Title: Business-Driven IT-Wide Agile (Scrum) and Kanban (Lean) Implementation
  • Author(s): Andrew Thu Pham, David Khoi Pham
  • Release date: August 2012
  • Publisher(s): CRC Press
  • ISBN: 9781466557499