Change Control Plan

1. Purpose of this Document

The purpose of the Change Control Plan is to set forth requirements and a course of action to follow to get changes to the product approved by management (Professor Henderson and/or Brandt).

2. Change Control Board

The Change Control Board will consist of all members of the Design Bug development team (Kip, Brian, Casey, and Jacob). Any decisions the Change Control Board makes will be taken to management (Professor Henderson and/or Brandt) for review and approval.

3. Procedure

• The Change Control Board will meet every week (Wednesday at 3:00 P.M. unless other arrangements are made).

• The members of the Change Control Board will propose possible changes to the project

• The board will discuss the possible changes and assess the benefits and drawbacks.

• After discussing a possible change the board will decide to accept, reject, or defer the change.

• If the change is accepted the board must decide if it is a small change or significant change. If the changed is deemed small the development team will go ahead and implement the change. (A small change consists of those that do not have far-reaching impacts, such as minor defect corrections. See Software Project Survival Guide p. 79)

• If the change is deemed significant the board will meet with management (Professor Henderson and/or Brandt) to present the change proposal to them.

• The Change Control Board will then implement or not implement the changes based on management's decisions and suggestions.

4. Change Consideration

The Change Control Board will consider at least the following factors when considering a change.

• What is the expected benefit?

• How would the change affect the project's schedule?

• How would the change affect the software's quality?

• How would the change affect the team's work distribution?

• Can the change be deferred to a later stage?

• Would the change risk destabalizing the software?