Change Request Documentation and Tracking

Correct Answer: Log change, assess impact, get approval, update baseline, communicate changes

The correct sequence for processing a schedule change request follows a logical progression: 1. Log the change first to ensure proper documentation and tracking from the start 2. Assess impact to understand the full implications on the project schedule and other constraints 3. Get approval from appropriate stakeholders based on the impact assessment 4. Update the schedule baseline once approval is received 5. Communicate changes to all relevant stakeholders This sequence ensures proper control, documentation, and communication throughout the change process. The other options are incorrect because: - Updating the baseline before getting approval violates change control principles - Assessing impact before logging the change lacks proper documentation from the start - Creating performance reports or documenting lessons learned are not primary steps in schedule change processing The correct sequence aligns with PMI's emphasis on controlled change management and proper stakeholder engagement.

Correct Answer: Assign unique identifiers to changes and link them to associated schedule elements

Assigning unique identifiers to changes and linking them to associated schedule elements is the most effective method because: 1. It ensures traceability of each change request 2. It maintains clear relationships between changes and affected schedule components 3. It facilitates impact analysis of changes 4. It enables proper version control and audit trails The other options are less effective because: Recording modifications with timestamps only captures when changes occurred but doesn't establish clear relationships between changes and schedule elements. Updating the baseline and documenting changes is a result of approved changes rather than a tracking method. Creating a log of variances focuses on impacts after the fact rather than managing the change control process itself. The best practice is to have a unique identifier system that connects each change to specific schedule elements, allowing for proper tracking, analysis, and control throughout the project lifecycle.

Correct Answer: Recording the impact analysis and maintaining sequential version control of all schedule modifications

The best practice for documenting change requests impacting schedule baselines involves two key elements: 1. Recording the impact analysis - This ensures all potential effects of the change are documented and understood 2. Maintaining sequential version control - This creates a clear audit trail of schedule modifications This approach is optimal because: - It maintains historical records of all changes - It provides clear traceability - It supports future analysis and lessons learned - It aligns with PMI's change control best practices The other options are incorrect because: - Maintaining parallel schedule versions can create confusion and version control issues - Using only automated notifications and central repositories falls short of proper impact analysis documentation - Creating variance reports and rolling wave planning doesn't address the core requirement of documenting change requests properly