Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
19 Cards in this Set
- Front
- Back
Three Types of Change Requests
|
Corrective Actions
Preventive Actions Defect Repairs |
|
Corrective Actions
|
Bring the work of the project into alignment with the project plan.
|
|
Preventive Actions
|
Implemented to help reduce the probability of a negative risk event.
|
|
Defect Repairs
|
Either correct or replace components that are substandard or malfunctioning.
|
|
Change Control System
|
Documented procedures that describe and manage the documentation required to request and track the changes and the updates to the project plan. Uses Integrated change control technique. Three big project killers.
|
|
Three Big Project Killers
|
Inadequate planning
Poor risk planning Inadequate change control processes |
|
Integrated Change Control
|
Looks at the impact of any change across all aspects of the plan. Impacts have an impact on the triple constraints, scope, or any combination of these factors.
|
|
Three Constraints
|
Time
Cost Quality |
|
Change Management System process includes
|
Change request forms (and other documentation)
Change request log Analysis of impacts of change CCB Coordination and communication with stakeholders Updating affected project-planning documents |
|
Change Request Documentation
|
After PM plan is approved, all change requests must go through the change control system. Change requests should always be in writing. A form will be provided to document them, the reason change is needed, and the impact if the change is not made.
|
|
Change Request Log: What should happen when Change request is submitted
|
It should be assigned an identifying number for tracking.
Recorded in the change request log. An analysis of the change request. |
|
Analyzing Change
|
Analyzed by experts working on the change request impacts, with input from the PM. Specific elements of the change request should be analyzed (equipment, resource hours, etc). PM will analyze the schedule, budget, and resource allocations to determine impacts. Info is presented to the CCB for approval or rejection.
|
|
Emergency Change
|
Established separate procedures. Includes description and definition of an emergency, authority level of PM, and process for reporting the change after. Requires follow-up with CCB and completion of formal change request.
|
|
Four Elements of Change
|
Resource changes
Requirements changes Infrastructure changes Configuration changes |
|
Resource Change
|
When a team member is added or leaves, important to document the reason, the name of replacement, person requesting change, and impact.
|
|
Requirements Change
|
As detail is added or updated to clarify expectations, make sure they do not involve a scope change. New requirements go through the change control process.
|
|
Infrastructure Change
|
Infrastructure remains permanently after the project is completed. Components that may change include: Computing systems, Software development environment, Server operating platforms, etc. Infrastructure changes can have a major impact on overall project plan.
|
|
Configuration Change
|
Design teams will sometimes make a decision about a software or hardware configuration only to find out that another configuration would work better.
|
|
Change Control Board (CCB)
|
Established to review all change requests. Includes stakeholders, managers, team members, and others who have a connection to the project. Change request and the impact analysis are given to the board for review to approve, deny, or delay it. Note their decision on the change request log.
|