ISBN 9788184041835,Ship It!: A Practical Guide to Successful Software Projects

Ship It!: A Practical Guide to Successful Software Projects



Shroff Publishers & Distributors Pvt Ltd

Publication Year 2009

ISBN 9788184041835

ISBN-10 8184041837

Paper Back

Number of Pages 220 Pages
Language (English)

Computer software

Ship It! helps teams get software out the door. Here you'll find a wealth of solid, practical advice in an easy, approachable format. You can fix many of the common problems facing software projects today with this concise introduction: you'll see the tools a successful team has to use, and learn how to use them well. You'll get quick, easy-to-follow advice on modern techniques and when they should be applied. Your team will be able to Ship It!Full DescriptionShip It! is a collection of tips that show the tools and techniques a successful project team has to use, and how to use them well. You'll get quick, easy-to-follow advice on modern practices: which to use, and when they should be applied. This book avoids current fashion trends and marketing hype; instead, readers find page after page of solid advice, all tried and tested in the real world.

Aimed at beginning to intermediate programmers, Ship It! will show you:
Which tools help, and which don't
How to keep a project moving
Approaches to scheduling that work
How to build developers as well as product
What's normal on a project, and what's not
How to manage managers, end-users and sponsors
Danger signs and how to fix them
Few of the ideas presented here are controversial or extreme; most experienced programmers will agree that this stuff works. Yet 50 to 70 percent of all project teams in the U.S. aren't able to use even these simple, well-accepted practices effectively. This book will help you get started.Ship It! begins by introducing the common technical infrastructure that every project needs to get the job done. Readers can choose from a variety of recommended technologies according totheir skills and budgets. The next sections outline the necessary steps to get software out the door reliably, using well-accepted, easy-to-adopt, best-of-breed practices that really work.Finally, and most importantly, Ship It! presents common problems that teams face, then offers real-world advice on how to solve them.
About the Author
Jared Richardson is a programmer, speaker, author, and trainer. He helps teams build better software through his company Agile Artisans. In addition to this book, he's a contributer to the No Fluff Just Stuff Anthology 2006 and 2007 editions. Since becoming an independent consultant, Jared spends most of his time trying to avoid mowing the grass.
Will Gwaltney is a software developer with over 20 years experience. In that time he hasn't quite seen it all, but he's seen most of it (and a lot of it hasn't been pretty). He's worked at both large companies and start-ups in the fields of electronics CAD, networking, telecommunications, knowledge representation, and web-based planning and scheduling for the enterprise. Will currently works on test automation at SAS Inc., the largest privately-owned software company in the world.

Table Of Contents:

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