🔄 Perform Integrated Change Control

🧩 What is Perform Integrated Change Control?

• Evaluates all change requests on a project to accept, reject, or defer them.
• Focuses on assessing the impact of changes on ALL project constraints: Scope, Quality, Risk, Schedule, Cost, Resources, Customer Satisfaction.
• Ensures approved changes update project plans, baselines, and artifacts.
• Changes after project charter and plan approval require formal evaluation.
• Helps reduce the risk of not meeting project objectives by controlling change impacts holistically.

⚙️ When is it used?

🛑 Why is this important?

• Changes impact multiple project constraints — not just one.
• Ignoring full impact causes hidden risks and failures.
• Cost of change increases over time — managing early saves $$$.
• Prevents chaos by requiring evaluation, approval, and controlled implementation.

💡 Key Concept: Impact Assessment

When a change is proposed, ask:
🔎 How does it affect:

• Scope?
• Quality?
• Risk?
• Schedule?
• Cost?
• Resources?
• Customer satisfaction?

📝 Change Categories & Approval

🏛️ Change Control Board (CCB)

• Group of decision makers: project manager, sponsor, customer, experts, etc.
• Reviews, approves, defers, or rejects change requests.
• Records decisions in the change log.

🛠️ Summary Process for Managing Changes

🔄 Detailed Process for Change Control

1. Prevent root causes to minimize unnecessary changes.
2. Identify need for change from any stakeholder or performance measurement.
3. Evaluate impact across all project constraints.
4. Create formal change request following change management plan.
5. Perform integrated change control:
   • Assess if change fits project charter & benefits project
   • Use cost-benefit & alternative analysis
   • Find options to minimize impact (crashing, cutting scope, etc.)
6. Approve/reject/defer change by project manager or CCB/sponsor.
7. Update change log with decision & reasons.
8. Update project plans, baselines, and documents as needed.
9. Communicate change to affected stakeholders.
10. Manage project execution according to revised plans.

🔀 Agile & Hybrid Environments

• Streamlined change control with many small changes daily.
• Product Owner has more approval authority.
• Minor changes handled within the team; major changes escalate to sponsors or steering committee.
• Still requires careful planning & management of significant changes.

✅ Best Practices for Plan-Driven Projects

• Obtain complete requirements early.
• Keep looking for missed stakeholders or requirements.
• Spend sufficient time on risk management.
• Establish schedule & cost reserves.
• Have a formal change process & templates.
• Define clear approval roles.
• Allow only approved changes to proceed.
• Reevaluate business case if changes are excessive.
• Consider terminating if changes undermine project viability.

🎨 Visual & Teaching Tips

• Titles in dark blue with underline
• Key points in bold with icons
• Use red or orange for warnings, green for best practices
• Tables with alternating row colors (light gray & white)
• Highlight important terms with color blocks or bold font
• Include callout boxes for "Think About It!" and examples
• Flowchart style graphic for the change control process steps