0%

Book Description

Agile Values and Principles for a New Generation

“In the journey to all things Agile, Uncle Bob has been there, done that, and has the both the t-shirt and the scars to show for it. This delightful book is part history, part personal stories, and all wisdom. If you want to understand what Agile is and how it came to be, this is the book for you.”

—Grady Booch

 

“Bob’s frustration colors every sentence of Clean Agile, but it’s a justified frustration. What is in the world of Agile development is nothing compared to what could be. This book is Bob’s perspective on what to focus on to get to that ‘what could be.’ And he’s been there, so it’s worth listening.”
—Kent Beck

 

“It’s good to read Uncle Bob’s take on Agile. Whether just beginning, or a seasoned Agilista, you would do well to read this book. I agree with almost all of it. It’s just some of the parts make me realize my own shortcomings, dammit. It made me double-check our code coverage (85.09%).”
—Jon Kern

Nearly twenty years after the Agile Manifesto was first presented, the legendary Robert C. Martin (“Uncle Bob”) reintroduces Agile values and principles for a new generation—programmers and nonprogrammers alike. Martin, author of Clean Code and other highly influential software development guides, was there at Agile’s founding. Now, in Clean Agile: Back to Basics, he strips away misunderstandings and distractions that over the years have made it harder to use Agile than was originally intended.

Martin describes what Agile is in no uncertain terms: a small discipline that helps small teams manage small projects . . . with huge implications because every big project is comprised of many small projects. Drawing on his fifty years’ experience with projects of every conceivable type, he shows how Agile can help you bring true professionalism to software development.

  • Get back to the basics—what Agile is, was, and should always be
  • Understand the origins, and proper practice, of SCRUM
  • Master essential business-facing Agile practices, from small releases and acceptance tests to whole-team communication
  • Explore Agile team members’ relationships with each other, and with their product
  • Rediscover indispensable Agile technical practices: TDD, refactoring, simple design, and pair programming
  • Understand the central roles values and craftsmanship play in your Agile team’s success

If you want Agile’s true benefits, there are no shortcuts: You need to do Agile right. Clean Agile: Back to Basics will show you how, whether you’re a developer, tester, manager, project manager, or customer.

Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

Table of Contents

  1. Cover Page
  2. About This eBook
  3. Praise for Clean Agile
  4. Half-Title Page
  5. Series-Page
  6. Title Page
  7. Copyright Page
  8. Dedication
  9. Contents
  10. Foreword
  11. Preface
  12. Acknowledgments
  13. About the Author
  14. Chapter 1 Introduction to Agile
    1. History of Agile
    2. Snowbird
    3. Agile Overview
    4. Circle of Life
    5. Conclusion
  15. Chapter 2 The Reasons for Agile
    1. Professionalism
    2. Reasonable Expectations
    3. The Bill of Rights
    4. Conclusion
  16. Chapter 3 Business Practices
    1. Planning
    2. Small Releases
    3. Acceptance Tests
    4. Whole Team
    5. Conclusion
  17. Chapter 4 Team Practices
    1. Metaphor
    2. Sustainable Pace
    3. Collective Ownership
    4. Continuous Integration
    5. Standup Meetings
    6. Conclusion
  18. Chapter 5 Technical Practices
    1. Test-Driven Development
    2. Refactoring
    3. Simple Design
    4. Pair Programming
    5. Conclusion
  19. Chapter 6 Becoming Agile
    1. Agile Values
    2. The Menagerie
    3. Transformation
    4. Coaching
    5. Certification
    6. Agile in the Large
    7. Agile Tools
    8. Coaching—An Alternative View
    9. Conclusion (Bob Again)
  20. Chapter 7 Craftsmanship
    1. The Agile Hangover
    2. Expectation Mismatch
    3. Moving Apart
    4. Software Craftsmanship
    5. Ideology versus Methodology
    6. Does Software Craftsmanship Have Practices?
    7. Focus on the Value, Not the Practice
    8. Discussing Practices
    9. Craftsmanship Impact on Individuals
    10. Craftsmanship Impact on Our Industry
    11. Craftsmanship Impact on Companies
    12. Craftsmanship and Agile
    13. Conclusion
  21. Chapter 8 Conclusion
  22. Afterword
  23. Index
44.201.97.224