Achieving Software Quality Through Teamwork

Successful software depends not only on technical excellence but on how members of the software team work together. Written in easy to understand language by a leading expert in the field, this ground-breaking volume provides an overview of the team culture required to develop quality software. Reflecting the different views on the nature of software quality, the book helps groups in a software team to communicate more effectively and to overcome the conflict created by their different perceptions of quality. You learn the roles and activities of team members (including customers) throughout the life of a software product, from before the software development starts and during the software development lifecycle, to after the software has been deployed and is in use.

Achieving SoftwareQuality through Teamworkdescribes popular software quality models such as EFQM,Watts Humphreys’ personal and team software processes, TMAP and CMM. Itfeatures numerous examples, sources for further information, and tools andtechniques that can be applied to real projects. An indispensable resource forsoftware developers, testers, managers, quality assurance professionals, andcustomers, the book explains how to clear the way through difficult “peopleissues” so that software quality can be achieved. Defining the key groupswithin a software team and their different definitions of quality, this uniquereference enables you to improve thecommunications and relationships between team members throughout a project andthe lifetime of the software.

Contents

Introduction.

SoftwareQuality Matters - Defining Software Quality. Fundamental Concepts of Excellence.EFQM Model. ISO9000:1994 and ISO9000:2000. IT Maturity Models - CMM andRelations. Team Software Process and Personal Software Process. Bringing theModels Together.

Definingthe Software Team - Teams in Disunity. Defining the Team. Interaction Between theGroups and Within Each Group.

Rolesand Quality: Customers - Introducing the Customers. Who Could Be in This Group.Quality Viewpoint. Quality Framework. Enablers for the Customers. Results forthe Customers. Life Cycle Activities. Summary of the Group.

Rolesand Quality: Managers - Introducing the Managers. Who Could Be in This Group.Quality Viewpoint. Quality Framework. Enablers for the Managers. Results forthe Managers. Life Cycle Activities. Summary of the Group.

Rolesand quality: Builders - Introducing the Builders. Who could be in This Group.Quality Viewpoint. Quality Framework. Enablers for the Builders. Results forthe Builders. Life Cycle Activities. Summary of the Group.

Rolesand quality: Measurers - Introducing the Measurers. Who could be in This Group.

QualityViewpoint. Quality Framework. Enablers for the Measurers. Results for theMeasurers. Life Cycle Activities. Summary of the Group.

Rolesand quality: Supporters - Introducing the Supporters. Who could be in This Group.Quality Viewpoint. Quality Framework. Enablers for the Supporters. Results forthe Supporters. Life Cycle Activities. Summary of the Group.

TheLifespan of a Software System - Lifespan or Life Cycle. Entry and Exit CriteriaBetween Stages. Changes in Quality Viewpoints Across the Lifespan of a System.

Start-upfor a Software Development - Start-up: description. Start-up Viewpoints. EntryCriteria for Start-up. Start-up: Typical Activities. Exit From Start-up Stage.

SoftwareDevelopment Life Cycle (SDLC) - SDLC Description. SDLC Viewpoints. Entry Criteria for SDLC. SDLC: typicalactivities. Entry and Exit Points Within the SDLC. SDLC Models. Quality Viewsand the Models - Why Combine Models. Exit From the SDLC. Conclusion.

Deliveryand Point-of-Live Support - Delivery: description. Delivery Viewpoints. EntryCriteria for Delivery. Delivery : Typical Activities. Exit From Delivery.Conclusion.

TheLife of a System Post Delivery - Post delivery: description. Delivery Viewpoints.Entry Criteria for Post Delivery. Post Delivery: Typical Activities. Exit FromPost Delivery. Conclusion.

Appendices - Toolsand Techniques. Organizations, Sources and References. Skeleton Documents,Forms and Outlines.

Isabel Evans is currently anindependent training provision and quality improvement consultant. She hasnearly 20 years experience in the IT industry, specializing in qualitymanagement, testing, training and documentation. She has aided organizations inthe development of standards, methods and procedures to support testing ofsoftware during development and maintenance projects. She has also providedquality assurance support, release management, and customer support for ITorganizations and has published extensively.