In 'Managing Software Quality and Business Risk' Martyn Ould travels further down the road on which he set out in his excellent 1990 book, 'Strategies for Software Engineering'. His basic premise then, and here, is that successful and achievable plans for software development must be based on both the assessment of risk and the achievement of quality - and the activities that flow from addressing these two concerns. The author has advice for us both as managers and engineers in this very readable book. His arguments are based on sound principles and amplified with excellent real-life anecdotes and experiences that bear out his ideas. He puts you in the driving seat and stands quietly behind you, giving you clear, well-considered, and, above all, practical advice on how to plan your software project. If you enjoyed his first book, this one is definitely for you. If you haven't yet read him, then do so now! Slightly disappointingly, the book does not set out to help you run your project. We could well do with such sensible advice here as well. How about another book, Martyn?
I read this book because the author teaches a Project Management course at Oxford University. His method is called STRADA, so I thought it might be useful to put on my cv. In fact the book says little new or exciting but very competently covers all the aspects of traditional project management. I have run more than 25 projects of up to 100 man years but still found it an engaging read. I recommend this to anyone new-ish to the subject. Follow this and you'll be doing the sorts of things common to most big structured IT organisations today. Well written and well researched but doesn't embrace the sorts of ideas in eg the Mythical Man Month (which you must buy if you haven't already).