You are previewing Practices of an Agile Developer.
O'Reilly logo
Practices of an Agile Developer

Book Description

These are the proven, effective agile practices that will make you a better developer. You'll learn pragmatic ways of approaching the development process and your personal coding techniques. You'll learn about your own attitudes, issues with working on a team, and how to best manage your learning, all in an iterative, incremental, agile style. You'll see how to apply each practice, and what benefits you can expect. Bottom line: This book will make you a better developer.

Table of Contents

  1. Practices of an Agile Developer
    1. Copyright
    2. For the Best Reading Experience...
    3. Table of Contents
    4. What readers are saying about Practices of an Agile Developer
    5. Chapter 1: Agile Software Development
      1. The Spirit of Agility
      2. The Practice of Agility
      3. The Devil and Those Pesky Details
      4. Acknowledgments
    6. Chapter 2: Beginning Agility
      1.   1   Work for Outcome
      2.   2   Quick Fixes Become Quicksand
      3.   3   Criticize Ideas, Not People
      4.   4   Damn the Torpedoes, Go Ahead
    7. Chapter 3: Feeding Agility
      1.   5   Keep Up with Change
      2.   6   Invest in Your Team
      3.   7   Know When to Unlearn
      4.   8   Question Until You Understand
      5.   9   Feel the Rhythm
    8. Chapter 4: Delivering What Users Want
      1.   10   Let Customers Make Decisions
      2.   11   Let Design Guide, Not Dictate
      3.   12   Justify Technology Use
      4.   13   Keep It Releasable
      5.   14   Integrate Early, Integrate Often
      6.   15   Automate Deployment Early
      7.   16   Get Frequent Feedback Using Demos
      8.   17   Use Short Iterations, Release in Increments
      9.   18   Fixed Prices Are Broken Promises
    9. Chapter 5: Agile Feedback
      1.   19   Put Angels on Your Shoulders
      2.   20   Use It Before You Build It
      3.   21   Different Makes a Difference
      4.   22   Automate Acceptance Testing
      5.   23   Measure Real Progress
      6.   24   Listen to Users
    10. Chapter 6: Agile Coding
      1.   25   Program Intently and Expressively
      2.   26   Communicate in Code
      3.   27   Actively Evaluate Trade-Offs
      4.   28   Code in Increments
      5.   29   Keep It Simple
      6.   30   Write Cohesive Code
      7.   31   Tell, Don’t Ask
      8.   32   Substitute by Contract
    11. Chapter 7: Agile Debugging
      1.   33   Keep a Solutions Log
      2.   34   Warnings Are Really Errors
      3.   35   Attack Problems in Isolation
      4.   36   Report All Exceptions
      5.   37   Provide Useful Error Messages
    12. Chapter 8: Agile Collaboration
      1.   38   Schedule Regular Face Time
      2.   39   Architects Must Write Code
      3.   40   Practice Collective Ownership
      4.   41   Be a Mentor
      5.   42   Allow People to Figure It Out
      6.   43   Share Code Only When Ready
      7.   44   Review Code
      8.   45   Keep Others Informed
    13. Chapter 9: Epilogue: Moving to Agility
      1. Just One New Practice
      2. Rescuing a Failing Project
      3. Introducing Agility: The Manager’s Guide
      4. Introducing Agility: The Programmer’s Guide
      5. The End?
    14. Appendix 1: Resources
      1. On the Web
    15. Bibliography