Q7 - Tell me - or really, the folk who've not read your book - a little more about the ins and outs of Ship It! What's in it for them for reading it? Who will enjoy reading it? Who won’t enjoy reading it?
Ship It is our take on the entire software ecosystem. Often a shop that does a great job in many different areas will have huge blind spots. Maybe a team has done a great job at following a process but ignores the infrastructure. Ship It! covers three major areas. Techniques, infrastructure, and process. You can see this in our poster of key practices http://media.pragprog.com/titles/prj/color_poster.pdf. The book also has a chapter of Frequently Asked Questions that talk about common scenarios you'll run into and how to use the key practices to solve those problems.
But it's not a religious diatribe on "The Right Way" to work. We tried very hard to introduce you to the reasons and ideas around following a process, then we suggest one you can use. I'm more about getting teams to use the ideas than to work like Will or me. We also covered the "what happens when you ignore this area" too.
Who should buy Ship It? The book was written as a guide for developers who wants to make a difference on their team, but it's been very popular with project managers and tech leads as well. In fact, it's often categorized as a project management book. I that's because there aren't a lot of ecosystem books out their and no one knows how to categorize it. :) It's not Java or C#. Must be.... project management!
Clarke: That's my last question for Jared for now. I've found Ship It! extremely useful and I thank Jared and William (his co-author) for their wonderful contribution.
Comments