Article: (CM) DESIGNING CHANGE REQUEST WORKFLOWS by Eric Mariacher

https://seir.sei.cmu.edu - 1 ABSTRACT
"Modern" software development companies use a change management tool. Configuration Management is one CMMI area. This paper deals with aspects of CM-SP2.1 “Track Change Requests” and CM-GP2.2 “Plan the Process”.
There are two kinds of possible change requests in a software: bug correction and feature implementation. Most of change management tools offer the possibility to implement a change request workflow to get visibility on the current status of the change request. In this article, simple to complex bug or feature development worflows will be built, based on answers given to a short list of questions and concerns.

Article: (CM) Need for Configuration Management by Harsha Chakravarti
https://seir.sei.cmu.edu - Configuration Management Needs
1. Overview
The goal of this process is to facilitate orderly management of product information about the assets and the changes to the assets that need to be controlled. Assets for Systems Development Resources (SDR) include software configuration items include, but are not limited to run-streams, code (COBOL, Powerbuilder, Java programs and executables), test plans (STP), Configuration Management Plans (CMP), software requirements (SRS/SRD, technical specifications) and design documents (SDD). CM is designed to ensure that organizations have the information they need to make sure their products perform as intended. The beneficial purposes of the Configuration Management Process, when implemented, include improvement of capability, performance, reliability and correction of defects.

Article: (CM) Configuration Management at an Off-Shore Software Development Center by Richard Gall, Abhay Saxena & Girish Khanzode

https://seir.sei.cmu.edu - Abstract
Software development deals with a continuum of change. The ability to deal with change when coupled with time-zone differences and physical distances presents a significant challenge in configuration management to of a development organization.

This paper examines the experiences of a multinational organization operating an offshore development center in India. The paper examines some of the issues that existed in the early stages of the setup of the center, as a strong and robust configuration management policy was developed. Some of the processes and policies put in place to address these issues are discussed. Intranet-based data capture, control and reporting systems were implemented along with strong process guidelines for source set management.
 
 

Article: (CM) Who’s Watching the Hen House? by Ron Starbuck

https://seir.sei.cmu.edu - Abstract
The answer to this question is a snap if your using the Software Engineering Institute’s (SEI) Software Capability Maturity Model® (SW-CMM) for software development. Software Configuration Management (SCM) may be the keeper of the keys to the product’s configuration, but it’s the Software Quality Assurance (SQA) Key Process Area (KPA) who ensures the approved, right products get in the Hen House and are maintained thereafter. Unfortunately, not every organization’s interpretation of the SW-CMM includes this not so obvious practice in their implementation. Sometimes even just getting SQA into place for them requires overcoming the misunderstanding that it polices quality into products. The purpose of this article is to examine how SQA ensures the software products developed are the right ones and how it interacts with the SCM Key Process Area to capture and maintain their integrity correctly in the Hen House.

(Read more)

Presentation: (CM) SCM: The Red-Headed Stepchild of the KPAs - How to Make SCM Feel Loved by Todd Holcombe, Bryan McMillan & Scott Ware
https://seir.sei.cmu.edu - Download