PK0-005 Question 1

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• 1

  Part 1 – Change Control Process Define new requirements and record changes Assess the schedule, risk, and cost Update and test the deliverable Perform a demonstration Part 2 – Documents to Update ✅ Statement of work ✅ Schedule ✅ Change log

• 2

  1. Define new requirements 2. Assess the schedule... 3. Consult the Raci Matric 4. Obtain sign off 5. Select the documents to update (already filled in, and branches into part 2) 6. Update and test the delverable 7. Perform a demonstration 8. Make an announcement Part 2: Issue log (the rejection is an issue) Change log (for the recommended/approved change Schedule (changed by the rejection) Statement of Work (assuming the scope changed based on new requirements) Risk register - Maybe? If the change creates new risks. Probably won't check this one. WBS dictionary - Maybe? If the change alters task definitions somehow? Probably won't check this one. Organizational Chart: No reason to check this one.

• 2

  Part 1: Top 4 Tasks Define new requirements and record changes: This is crucial as it sets the direction for all subsequent steps. Assess the schedule, risk, and cost: This is important to understand the impact of the changes. Update and test the deliverable: Ensuring the deliverable meets the new requirements is key. Obtain a sign off: This is necessary to confirm acceptance of the changes. Part 2: Top 4 Documents Risk Register: Updated to reflect any new risks associated with the changes. Schedule: Updated to reflect the time impact of the changes. Statement of Work (SOW): Updated to document the new requirements. Change Log: Updated to keep a record of what changes have been made.