Broken Agile

[Please advise Responsible Editor if any is needed]

A unique book of essays on the positives and negatives of agile software development Agile software development continues to be at the forefront of methodologies for today's software developers Tim Brizard has designed and developed enterprise level systems since 1997

Autorentext
Tim Brizard is a Software Engineer in Orlando, Florida. He has designed and developed enterprise level systems since 1997. His experience includes architecting solutions for both small and large companies alike. He started his programming career using COBOL, RPG, and Unix and then started to use object-oriented languages like C++ and Java (r). He has a comprehensive knowledge of object-oriented languages, distributed computing, and database solutions. His architecture experience ranges from simple client-server to n-tier applications. He has a passion for software delivery and teaching others about improving the quality of software.

Klappentext
Broken Agile, Second Edition 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.
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

  Inhalt

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