Description

Book Synopsis
Presenting common problems that teams face, this book also offers advice on how to solve them. It helps teams get software out the door and provides advice in an easy format. It is aimed at beginning to intermediate programmers and shows which tools help, and which don't, how to keep a project moving, approaches to scheduling that work, and more.

Trade Review
"Who should read it? Most people I think. It's aimed at technical leads certainly, but all developers would benefit by reading. I believe that project managers would benefit from having high-level familiarity with the book's ideas. I thoroughly enjoyed the book: I found it a pleasure to read and was particularly impressed with the layout and organization of the material. Recommended." - Harry Newton, news@UK, September 2005

Table of Contents
Foreword Preface 1 Introduction 1.1 Habitual Excellence 1.2 A Pragmatic Point of View 1.3 Road Map 1.4 Moving On 1.5 How Should I Read This Book? 2 Tools and Infrastructure 1. Develop in a Sandbox 2. Manage Assets 3. Script Your Build 4. Build Automatically 5. Track Issues 6. Track Features 7. Use a Testing Harness 8. On Choosing Tools 9. When Not to Experiment 3 Pragmatic Project Techniques 10. Work from The List 11. A Tech Leads 12. Coordinate and Communicate Every Day 13. Review All Code 14. Send Code Change Notifications 15. Putting It All Together 4 Tracer Bullet Development 5 Common Problems and How to Fix Them 16. Help! I've Inherited Legacy Code 17. Testing Untestable Code 18. Features Keep Breaking 19. Tests? We Stopped Using Them 20. But It Works for Me! 21. It Hurts When I Integrate Code 22. Can't Build the Product Reliably 23. Customers Are Unhappy 24. You've Got a Rogue Developer 25. Your Manager Is Unhappy 26. Team Doesn't Work Well Together 27. Can't Get "Buy-in" on Essential Points 28. The New Practice Didn't Help 29. There's No Automated Testing 30. We're Junior Developers, With No Mentor 31. We're on a "Death March" Project 32. Features Keep Creeping In 33. We're Never Done A Tip Summary B Source Code Management C Build Scripting Tools D Continuous Integration Systems E Issue Tracking Software F Development Methodologies G Testing Frameworks H Suggested Reading List H.1 Bibliography

Ship It A Practical Guide to Successful Software

    Product form

    £20.39

    Includes FREE delivery

    RRP £23.99 – you save £3.60 (15%)

    Order before 4pm today for delivery by Tue 4 Aug 2026.

    A Paperback / softback by Jared Richardson, William A Gwaltney

    Out of stock

      Trusted by thousands of customers. See 2,385+ Customer Reviews

      View other formats and editions of Ship It A Practical Guide to Successful Software by Jared Richardson

      Publisher: The Pragmatic Programmers
      Publication Date: Publication Date: 05/07/2005
      ISBN13: 9780974514048, 978-0974514048
      ISBN10: 0974514047

      Description

      Book Synopsis
      Presenting common problems that teams face, this book also offers advice on how to solve them. It helps teams get software out the door and provides advice in an easy format. It is aimed at beginning to intermediate programmers and shows which tools help, and which don't, how to keep a project moving, approaches to scheduling that work, and more.

      Trade Review
      "Who should read it? Most people I think. It's aimed at technical leads certainly, but all developers would benefit by reading. I believe that project managers would benefit from having high-level familiarity with the book's ideas. I thoroughly enjoyed the book: I found it a pleasure to read and was particularly impressed with the layout and organization of the material. Recommended." - Harry Newton, news@UK, September 2005

      Table of Contents
      Foreword Preface 1 Introduction 1.1 Habitual Excellence 1.2 A Pragmatic Point of View 1.3 Road Map 1.4 Moving On 1.5 How Should I Read This Book? 2 Tools and Infrastructure 1. Develop in a Sandbox 2. Manage Assets 3. Script Your Build 4. Build Automatically 5. Track Issues 6. Track Features 7. Use a Testing Harness 8. On Choosing Tools 9. When Not to Experiment 3 Pragmatic Project Techniques 10. Work from The List 11. A Tech Leads 12. Coordinate and Communicate Every Day 13. Review All Code 14. Send Code Change Notifications 15. Putting It All Together 4 Tracer Bullet Development 5 Common Problems and How to Fix Them 16. Help! I've Inherited Legacy Code 17. Testing Untestable Code 18. Features Keep Breaking 19. Tests? We Stopped Using Them 20. But It Works for Me! 21. It Hurts When I Integrate Code 22. Can't Build the Product Reliably 23. Customers Are Unhappy 24. You've Got a Rogue Developer 25. Your Manager Is Unhappy 26. Team Doesn't Work Well Together 27. Can't Get "Buy-in" on Essential Points 28. The New Practice Didn't Help 29. There's No Automated Testing 30. We're Junior Developers, With No Mentor 31. We're on a "Death March" Project 32. Features Keep Creeping In 33. We're Never Done A Tip Summary B Source Code Management C Build Scripting Tools D Continuous Integration Systems E Issue Tracking Software F Development Methodologies G Testing Frameworks H Suggested Reading List H.1 Bibliography

      Recently viewed products

      © 2026 Book Curl

        • American Express
        • Apple Pay
        • Diners Club
        • Discover
        • Google Pay
        • Maestro
        • Mastercard
        • PayPal
        • Shop Pay
        • Union Pay
        • Visa

        Login

        Forgot your password?

        Don't have an account yet?
        Create account