- Series: Pragmatic Programmers
- Paperback: 208 pages
- Publisher: Pragmatic Bookshelf; 1 edition (June 11, 2005)
- Language: English
- ISBN-10: 0974514047
- ISBN-13: 978-0974514048
- Product Dimensions: 7.5 x 0.8 x 9.2 inches
- Shipping Weight: 14.4 ounces (View shipping rates and policies)
- Average Customer Review: 29 customer reviews
- Amazon Best Sellers Rank: #1,254,894 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ $3.99 shipping
+ $3.99 shipping
+ $3.99 shipping
Ship it! A Practical Guide to Successful Software Projects Paperback – June 11, 2005
|New from||Used from|
"The Other Woman" by Sandie Jones
“The Other Woman is an absorbing thriller with a great twist. A perfect beach read.” ― Kristin Hannah, #1 New York Times bestselling author of "The Great Alone" Pre-order today
Frequently bought together
Customers who bought this item also bought
""It's rare to have this much fun reading a book about software. The ideas are smart, relevant, and fundamental. I can be a better programmer today because of the things I read today.""--Joe, Fair Developer
""A great book! The authors have done a great job in presenting the subject in a neutral way and avoiding any methodology-oriented traps.""--Roberto Gianassi, IT Consultant
""This is fantastic stuff. As I started reading, I almost fell out of my seat because the project I'm on right now is going through exactly the hurt you describe and would benefit greatly from material just like this.""--Matthew Bass, Software Engineer
About the Author
Jared Richardson is a developer-turned-manager who thinks a good day is having everything delegated so that he can sneak away and actually write code. He specializes in using off-the-shelf technologies to solve tough problems, especially those involving the software development process. With more that 10 years of experience, Jared has been a consultant, developer, tester, and manager, including Director of Development at several companies. He currently manages a team of developers and testers at SAS Institute, and is responsible for a company-wide effort to use test automation to improve the quality of SAS products. Will Gwaltney is a software developer with over 20 year's 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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
If you and your team already are using source management, doing code reviews, and writing tests that you frequently use (chances are you probably follow most if not all of the best practices in the book) and if you have read more generic time/project management books many of the management tips probably will not be new either. If your development process is not a well oiled automated machine or perhaps struggle with team communication you will find the book very helpful and enjoyable readable.
Despite being familiar with most of the items put forth in the book, I especially enjoyed the trace bullet development chapter. That method of development struck a good balance between planning out the software and completing it in stages concurrently rather than focusing a teams effort only on one interface/module at a time.
While I was familiar with most of the content and practices of the book I would still highly recommend it for both developers and managers (actually anyone who works at a software company could probably benefit from reading it).
The list of critical practices are well defined and each one is simple enough to implement. It makes you feel like maybe you could do it. Most important, it explains why you should do it - in compelling terms so that even if you are skeptical of "continuous integration" or "pair programming" or "unit tests", well, you won't be after you read this book.
"Tracer Bullet" development isn't another methodology, but a way of incrementally developing a project so that the status is more clear to the customer and so that you can quickly turn abstract ideas that the team has into something more concrete to react to. In doing so, you maintain an integrated view of the product you are working on and help people understand their ideas more quickly. It is priceless for any non-trival software. Most of us probably have learned to do this anyway, but now there is a name for it and a guide to understand why we do what we learned through trial and error.
Most of it corroborated the practices we have seen to work. The rest showed where we can make amends for better results. I recommend it wholeheartedly to every project manager, technical architect, and strategic thinker at IT companies.
Had it been one of my first project management books I would have rated it higher.
It's a quick and easy read, good beginner material. It may be a little "lightweight" for some.
If you are a student or just a beginner trying to understand how real-world software is made, you should read it.
For me, it was just a waste of time and 20 bucks.
The following book is a ten-star work of art aimed at software engineering students learning Java: Agile Java : Crafting Code with Test-Driven Development by Jeff Langr
The ten-star artwork for Agile processes in general is Craig Larman's astonishing work: Agile & Iterative Development.
Most recent customer reviews
Like the 'The Pragmatic Programmer: From Journeyman to Master' is for programmer,...Read more