What should be covered in an implementation when the change is approved? ISEB ISEB-PM1 Exam

Question

Options

• AFunctional requirement
• BStatus report
• CCustomer need
• DDefect repair

• A
  4% (1)
• B
  15% (4)
• C
  7% (2)
• D
  74% (20)

Explanation

In change control processes (a core ISEB PM1 topic), an approved change typically originates from an identified defect - so when the change moves into implementation, what is actually carried out is the defect repair that was scoped and authorized through the change request. This ties directly to configuration management: the approved change authorizes fixing a known flaw, and implementation is where that fix is delivered.

Why the distractors are wrong:

• A. Functional requirement - Requirements are captured during planning/analysis, not enacted during an approved change implementation.
• B. Status report - A status report is a monitoring and communication output, not something "implemented" as part of a change.
• C. Customer need - Customer needs drive requirements upstream; by the implementation stage, those needs have already been translated into deliverables and change requests.

Memory tip: Think of the change control cycle as a loop - a defect is found → a change is requested → the change is approved → the defect is repaired. The word "repair" anchors the implementation step to the defect that triggered the change in the first place.

No community discussion yet for this question.