Achieving Software Quality through Teamwork (Artech House Computing Library) [Hardcover]

Isabel Evans is an internationally known speaker on quality aspects of software development. I have heard her speak, both in the UK and abroad, and she talks good common sense. The pleasing aspect about this book is that it emphasises the partnership aspects of software, that we succeed together. The final sentences are worth repeating: " ..... communication and team work are key to achieving software quality. It is not my responsibility, and it is not your responsibility. It is our responsibility. Together."

There are 3 parts to the book. After introducing 5 views of quality, the partners in the software production process are described. This concentrates on how these groups can help each other, and what views of quality each is generally looking at. Finally, four generally recognised parts of the process are described. It is not until the three parts come together, with a common understanding, that quality happens. Quality has to be planned, it doesn't just happen. Isabel reminds us that the post implementation stage of a software project is usually the longest, and that there are software systems that have been in production for upwards of 20 years [which, incidentally, was the cause of the panic around `the millennium bug']

The partners in the process are described in detail, and the names of these groups may not be immediately recognisable. Evans uses `builders', `measurers' and `supporters', and using unfamiliar terms can cause readers to sit bolt upright and think. `Builders' includes more than what has been generally described as development staff, and the different name drives this home. There is plenty of first and second hand experience, including the embarrassing tactless remarks of Isabel herself as a junior software tester. The limited use of persona works well; `Simon Tester' and `Jo Senior Tester' immediately give a mental picture of those involved. In the partnership aspects, it is stressed that testers are not the most important people in the world, and that they can be wrong. We in testing need to remember that.

After the first chapter, each can be read on its own. This of itself can cause a few stylistic problems (every time `SDLC' is mentioned, the abbreviation is spelt out as the Software Development Life Cycle), but minor irritations of this nature would be picked up by a fellow tester, wouldn't they. There is plenty to make you think, presented in a matter-of-fact way, including some real gems: "keep repetitions across documents to a minimum, as it saves reading and update time". You can almost HEAR her as you read that, and that one sentence should be pasted in 3 foot high letters on the wall of many firms. Some of Isabel's favoured topics are covered (e.g. the value of diagrams to inform / mis-inform), and there are wonderful references, and pointers to further reading in the Appendices. This includes some `tester' topics such as document reviews and test automation, but also more general subject matter - e.g. Edward de Bono's Thinking Hats and Meridith Belbin's team roles.

If you work in the broad software development arena, this book will do you good. It is an extremely worthwhile addition to the bookshelf of any ICT professional. Read it, practice it, and lend it. Do not leave it on the bookshelf.

Peter Morgan, Bath, UK (...)

› Go to Amazon U.S. to see the review  5.0 out of 5 stars