Broken Agile: 2nd Edition

This brief book contains stories from years of real world experience on Agile teams and projects. It contains both good and bad examples of how Agile can be adopted. The stories in each chapter are both educational and can also be entertaining. Each chapter focuses on specific Agile values and principles. The stories in each chapter are used to illustrate how Agile values and principles are sometimes misunderstood or applied on Agile teams and projects. In Broken Agile, Second Edition, you’ll read how Agile is used in the real world and the consequences of poor adaptations of the Agile Software Development methodology. You will also read examples of how some companies have been successful in adopting Agile. The goal is to share stories that will help Agile teams in their journey to adopt Agile Software development.

What You’ll Learn

• What are good and bad examples of how Agile can be adopted
• What are some specific Agile values and principles
• How some of these are misunderstood or applied – correctly or incorrectly
• How Agile is used in the real world
• What are the consequences of poor adaptations of the Agile software methodology
• What are examples of how some companies have been successful in adopting Agile

Audience

This book is for experienced software developers in their journey to adopt Agile Software development. It is very useful for those considering implementation of Agile processes.

Table of Contents

Chapter 1: Introduction
Chapter 2: Scale Success
Chapter 3: Communication
Chapter 4: Poor Foundations
Chapter 5: Long-Run Plan for Success
Chapter 6: Adjusting in Time
Chapter 7: Sending the Wrong Signals
Chapter 8: Balancing Life and Work
Chapter 9: Fake It Until You Make It
Chapter 10: Building Unity
Chapter 11: Keeping Engaged
Chapter 12: Fundamental Misunderstandings
Chapter 13: Challenges with Estimations
Chapter 14: Transparency
Chapter 15: Specifications and Testing
Chapter 16: Some Process Required
Chapter 17: Physical vs. Virtual
Chapter 18: Final Thoughts