As the hypothesized value of new process elements is proved by pilot projects, the SEPG should prepare for broad deployment and subsequent implementation. Many organizations make the process elements available via the Web and expect that the projects will simply start using them. This Field of Dreams approach ("if you build it, they will come") is intuitively appealing to the SEPG, but rarely proves to be an effective or efficient means of changing people's behavior.
Other organizations follow a strategy similar to that employed for their software packages. These organizations package multiple new or modified process elements into periodic "process releases," and accompany each release with release notes, testimonial data from the pilot projects, process training, internal consultation, and a great deal of fanfare. Typically, these process releases are made one to four times per year. This approach provides sufficient process stability and ensures that project personnel aren't constantly struggling to figure out what today's process is.
Regardless of the deployment approach, as new process elements are released, the SEPG should monitor the project adoption rate ”the rate at which the new process elements are being adopted by the project teams . The primary question addressed by measuring the adoption rate is: How many of the projects that should be using these new elements are using them?
The SEPG should seek to apply process improvement concepts to its own processes (" physician , heal thyself "), one of which is the deployment process. In an effort to provide better services in the future, the SEPG should ask a series of secondary questions related to the adoption rate such as:
The data derived from the answers to such questions can be analyzed to accelerate the adoption of the current process release as well as to enhance the means of releasing new process elements in the future.
What Is Software Quality?
Software Development Process Models
Fundamentals of Measurement Theory
Software Quality Metrics Overview
Applying the Seven Basic Quality Tools in Software Development
Defect Removal Effectiveness
The Rayleigh Model
Exponential Distribution and Reliability Growth Models
Quality Management Models
In-Process Metrics for Software Testing
Complexity Metrics and Models
Metrics and Lessons Learned for Object-Oriented Projects
Measuring and Analyzing Customer Satisfaction
Conducting In-Process Quality Assessments
Conducting Software Project Assessments
Dos and Donts of Software Process Improvement
Using Function Point Metrics to Measure Software Process Improvements
A Project Assessment Questionnaire