While implementing an approved change, a critical defect was introduced. Removing the defect will delay the product delivery. What is the MOST appropriate approach to managing this situation?

Question

Options

• AUtilize the change control process.
• BCrash the schedule to fix the defect.
• CLeave the defect in and work around it.
• DFast-track the remaining development.

• A
  72% (38)
• B
  8% (4)
• C
  17% (9)
• D
  4% (2)

Explanation

Option A is correct because any deviation from the approved change - including a defect that affects scope, schedule, or quality - must be handled through the change control process, which exists precisely to evaluate impacts, obtain authorization, and update the project baseline formally. Crashing the schedule (B) adds resources and cost without proper authorization, which itself would require a change request anyway and treats the symptom rather than the process. Leaving the defect in (C) violates quality standards and creates undocumented technical debt, essentially bypassing governance entirely. Fast-tracking (D) overlaps activities to save time but doesn't address the defect and similarly bypasses the proper approval process.

Memory tip: Whenever a question describes an unplanned situation that affects the project baseline (scope, time, cost, quality), the answer almost always routes through the change control process - it's the PM's go-to response for any mid-project surprise requiring a decision.

No community discussion yet for this question.