Software Process Improvement: Practical Guidelines for Business Success

Dear Readers of Zahran's book: I am the author and the publishers have plans to publish a new edition which reflects the new CMMI and SCAMPI (instead of CMM and CBA). Until the new edition is ready, I can send any reader of the book a copy of the drafts of the new chapters. Please write to me on the following email: [email protected] requesting the new chapters and I will send them to you as a compliment for reading my book.

This book provides a very good practical reference for business. I particularly like the step by step guidance on creating an SPI (Software Process Improvement) action plan in Chapter 9. The action plan provides a nice conclusion to part 2 ( a framework for software process improvement). By the way congratulations on providing a framework for SPI. Coming from a development background I know how difficult it was to arrive at a framework for a modern Software Development Process (SDP), let alone SPI. For example, DSDM (Dynamic Systems Development Method) the current UK defacto standard,(launched 1995) took a quarter of a century to arrive. But I digress. From a business point of view you cannot control what you cannot measure let alone derive any benefit from it. As Dr Sami states in Chapter 12 (Measuring the benefits of software process improvement): "One of the major obstacles to the adoption of SPI is the reluctance of business management to invest ... because they do not have convincing evidence of the return on investment." This is soon remedied in this same chapter as Dr Sami states: "This chapter provides a summary of the evidence of the business benefits of SPI." with useful examples of process-related, project-related, product-related and customer-related measures. I would certainly recommend putting all that data in a database (e.g. SQL Server or Oracle) for analysis and, using a Service-Oriented Architecture view, providing the whole package as a service to the business. The data including graphs, charts, reports etc. could be nicely presented in a browser. Perhaps Dr Sami could provide a chapter or book about software support for SPI. But I digress again. Evidence of business benefits does not stop in Chapter 12, but is continued in Chapter 19 (The evidence: business benefits of software process improvements) with facts and figures from the US Air Force, Hughes Aircraft and Raytheon's investments in SPI and gained direct benefits. In Chapter 20 (Epilogue: future of SPI) Dr Sami advocates "Process discipline" as "a prerequisite for industrialisation". He mentions how process discipline is a necessary foundation for software industrialisation, with all the benefits that can bring. This is compared to the benefits of mass production brought about by manufacturing industry during the industrial revolution. How prophetic. Certainly with business-oriented initiatives such as the OMG's (Object Management Group - see www.omg.org) introduction of Model-Driven Architecture (MDA - see www.omg.org) and other software industry efforts for the continuous improvement of the SDP in order to bridge the semantic gap between users and developers and bring the whole process that much closer to the business, a software blueprint might actually emerge. This is a good, thought provoking reference that I shall keep in my library for many years to revisit time and time again.

This book is the best implementation guide on the market for Software Process Improvement. Whether you're a fledgling company trying to design quality software with no guidelines to go by or a well-developed organization with processes in place, this book offers up many ways you can improve your software quality. It gives you a benchmark to compare your company with ISO 9001, CMM and others which is invaluable. If you're looking for help bringing your software processes into alignment - you want this book!

This book describes clearly the concepts behind the most popular Software Process Improvement models and standards.

This book is an excellent reference source for understanding the concepts, issues, and initiatives concerning information system process improvement. It is well organized and flows logicallly. It is especially an excellent source document for managers who are responsible for setting the overall direction of their company's IT programs. The book should be read by anyone who is concerned with software process improvement.