Skip to main content
SpringerLink
Log in
Apress
Book cover

Broken Agile

Second Edition

  • Book
  • © 2015

Overview

Authors:
  1. Tim Brizard
    View author publications

    You can also search for this author in PubMed   Google Scholar

  • 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

This is a preview of subscription content, log in via an institution to check access.

Access this book

Log in via an institution
eBook USD 19.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 24.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (18 chapters)

  1. Front Matter

    Pages i-ix
    Download chapter PDF

  2. Introduction

    • Tim Brizard
    Pages 1-2

  3. Scale Success

    • Tim Brizard
    Pages 3-5

  4. Communication

    • Tim Brizard
    Pages 7-14

  5. Poor Foundations

    • Tim Brizard
    Pages 15-18

  6. Long-Run Plan for Success

    • Tim Brizard
    Pages 19-22

  7. Adjusting in Time

    • Tim Brizard
    Pages 23-26

  8. Sending the Wrong Signals

    • Tim Brizard
    Pages 27-31

  9. Balancing Life and Work

    • Tim Brizard
    Pages 33-36

  10. Fake It Until You Make It

    • Tim Brizard
    Pages 37-42

  11. Building Unity

    • Tim Brizard
    Pages 43-49

  12. Keeping Engaged

    • Tim Brizard
    Pages 51-53

  13. Fundamental Misunderstandings

    • Tim Brizard
    Pages 55-64

  14. Challenges with Estimations

    • Tim Brizard
    Pages 65-69

  15. Transparency

    • Tim Brizard
    Pages 71-74

  16. Specifications and Testing

    • Tim Brizard
    Pages 75-82

  17. Some Process Required

    • Tim Brizard
    Pages 83-85

  18. Physical vs. Virtual

    • Tim Brizard
    Pages 87-89

  19. Final Thoughts

    • Tim Brizard
    Pages 91-93

  20. Back Matter

    Pages 95-98
    Download chapter PDF
Back to top

Keywords

About this book

Learn how to be successful in adopting Agile and see good and bad examples of how Agile can be adopted. Broken Agile, Second Edition contains stories from years of real world experience on Agile teams and projects. The stories in each chapter are both educational and 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 misapplied on Agile teams and projects. You will read how Agile is used in the real world and the consequences of poor adaptations of the Agile software development methodology. These stories will help you in your 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 misapplied
  • How Agile is used in the real world
  • What are the consequences of poor adoption of the Agile software methodology
  • 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.


About the author

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.


Bibliographic Information

Publish with us

Policies and ethics

Back to top

Search

Navigation