Change Request

Change Management Procedures:

Identify Change: changes may be caused by many reasons, and most projects experience it during the project life cycle; Change may occur due to stakeholder requests, team member recommendations, vendor issues, risks, project constraints, and various others.

Document using the appropriate change control forms:

• Corrective Actions- aligns the work of the project with the project plan.
• Preventive Actions- reduces the possibility of a negative risk event.
• Defect Repairs- corrects or replaces components that are substandard or are malfunctioning.

Perform Impact Analysis:

• Should the change be implemented?
• What’s the cost to the project in terms of project constraints: cost, time, scope, and quality?
• Will the benefits gained by making the change increase or decrease the chances of project completion?
• What is the value and effectiveness of this change?
• Is there a potential for increased or decreased risk as a result of this change?

Changes to the Triple Constraints:

Time/Schedule- risks may cause time to be extended, that may result in becoming off schedule.

Cost/Resources- cost may rise; risks may cause you to use more resources.

Quality/Scope- quality may go down because you may start to rush, losing scope.

Risks:

Qualitative and quantitative risk analysis:

• Qualitative risk analysis- aligns risks in a priority order based on their effect on the project objectives
• Quantitative risk analysis- a complex technique that uses a mathematical approach to numerically analyze the probability and impact of risk events

Opportunities:

• Sharing- Assigning the risk to a third party who is best able to bring about the opportunity
• Exploiting- looking for opportunities to take advantage of positive impacts
• Enhancing- monitoring the probability or impact of the risk event to assure benefits are realized

Threats:

• Avoidance- avoiding the risk altogether or eliminating the cause of the risk event
• Acceptance- choosing to accept the consequences of the risk
• Mitigation- reducing the impact or the probability of the risk

Changes:

• Resource Changes- when a team member is added or leaves, remember to document reason for change, the name of the replacement, the person requesting the change, and any impact the change will have on the project.
• Requirements Changes- as detail is added to a requirement or it is updated to clarify expectations, you need to be taking a look at these changes to make sure they do not involve a scope change. Any new requirement should always go through the change scope process.
• Infrastructure Changes- Infrastructure is the element of a project that will remain permanently after the project is completed.
• Configuration Changes- simple or complex changes.

 

Resource Leveling Techniques:

• Fast Tracking- starting two tasks parallel that were schedule to start sequentially.
• Crashing- when you add resources to critical path tasks in order to shorten the project duration.
• Delaying- postpones the change request.
• Optimizing– to optimize risk components.

 

TestMoz:

Click here to take a test on this chapter.