Results from a process audit show that the requirements group does not control changes to...

When the requirements group does not control changes to software specifications, a basic requirement is to assign explicit responsibility for software configuration management (SCM) for each project. Here's why:

Clear Accountability: Assigning explicit responsibility ensures that someone is accountable for managing and controlling changes.

Consistency in Process: This ensures consistent application of SCM practices across different projects.

Improved Control: Clear responsibility helps in better monitoring and controlling changes, reducing the risk of unauthorized or untracked changes.

Policy Enforcement: Facilitates the enforcement of SCM policies and procedures, ensuring compliance and integrity of the project.

References:

"Software Configuration Management Patterns: Effective Teamwork, Practical Integration" by Stephen P. Berczuk and Brad Appleton.

"Software Configuration Management Strategies and Rational ClearCase: A Practical Introduction" by Brian A. White.