Question
During a gate review meeting, the deliverable was rejected by the customer.
Part 1: Place the tasks in the correct order based on the project change control process (Step 1 to Step 4). The available tasks are: Perform a demonstration; Define new requirements and record changes; Update and test the deliverable; Consult the RACI matrix; Assess the schedule, risk, and cost; Obtain a sign off; Make an announcement on the company portal.
Part 2: Select the proper document(s) to be updated: Risk register, Schedule, Statement of work, Organizational chart, Change log, Issues log, WBS dictionary.
Explanation
Step 1 is to define the new requirements from the customer's rejection and record the change, because change control starts by documenting the requested change. Step 2 is to assess its impact on schedule, risk and cost so the change can be evaluated before work begins. Step 3 is to update and test the deliverable against the new requirements, and Step 4 is to demonstrate it to the customer for acceptance; consulting the RACI matrix and announcing on the company portal are not change control steps. For the documents, the statement of work changes because the agreed scope and requirements changed, the schedule changes because rework takes time, and the change log records the change and its decision. The organizational chart, issues log and WBS dictionary are not the documents that capture an approved scope change in this scenario, and the risk register is only updated if the assessment identifies new risks.
