Finance-Software

This book is about the software quality methods and initiatives that have evolved in Europe. It's a collection of presentations that were given at three years of ISCN (International Software Collaborative Network)conferences.

Dr Richard Messnarz, the editor, did an excellent job of ensuring that the material is not only uniformly written, which in itself is no small task considering that there are over 30 contributors from 11 European countries. However, the way this book is organized reflects the real editorial genius. It's divided into three parts covering (1) principles (theory), (2) experience (practical application of the principles), and (3)synthesis and conclusion (what the future holds and how the European approach is different from the U.S. approach).

Chapter 1 is clear roadmap to the book and shows how the subsequent chapters tie together to form an alignment of principles and experience. More importantly, it also shows how technical aspects of the principles link to business issues. This is evident in Part 1 where chapters 2, 5, 6 and 7 address business-enabling topics, while chapters 3 and 4 focus in the underlying processes and methods to achieve them. My favorite chapters from this part of the book were 6-Process and Product Measurement, and 7-Costs and Benefits of Software Process Improvement. In particular, chapter 6 had clearly written guidance on project controls that is a pet interest.

Part 2 is devoted to the experience part that ties to the principles. The ten chapters cover thoroughly how the principles were employed at a variety of European companies. I like the cross-section that the editor includes, which covers big and small companies. This selection of case studies shows that size of the company does not matter as much as commitment to perform, which is the bottom line in any endeavor. This is where theory meets practice, and the case studies clearly show that the two can be aligned.

Part 3 is a single chapter that outlines the differences between the U.S. and European approaches to software quality and processes. It is interesting reading because the challenges are cultural and also hampered by national pride. However, from my perspective, which includes international consulting, the biggest cultural differences are company cultures and not national ones. Still, lessons can be learned from this chapter because you will see the same symptoms when comparing two different companies in, say, Los Angeles, as you will when comparing national cultures.

Overall: every one of the chapters is well written and thought provoking. The processes and methods, drawn from a large number of European initiatives, are true best practices. The case studies are not only illuminating from the perspective of someone who wants to implement mature processes, but they are also inspirational in that they show that it can be done in companies big and small. The biggest value, though, is the masterful way the editor has organized this book. The way principle is linked to experience, experience of large companies compared to that of smaller ones, and the array of approaches and methodologies presented make this book easy to use as a reference. I strongly recommend it and give it 5 stars.