Hybrid Project Change Control: First Step When Scope Change Requested | Project Management Professional Explained

• A.Add the request to the product backlog and prioritize it in the next sprint planning.
• B.Ask the development team to quickly estimate the effort and begin work if it can be accommodated without delaying the next release.
• C.Thank the stakeholder and explain that the request is out of scope; no changes can be made.
• ✓ D.Submit a change request to the change control board (CCB) and assess the impact on schedule, cost, and resources.

Why D: In a hybrid project, changes to scope after a sprint review must follow a formal change control process to protect the baseline. Option D is correct because the project manager should first submit a change request to the CCB to assess the impact on schedule, cost, and resources before any work begins, ensuring alignment with the project's governance framework.

• ✓ A.Perform an impact analysis and submit a change request to address the vulnerability
• B.Instruct the team to fix the vulnerability immediately without formal change control
• C.Ask the team to work overtime to fix the vulnerability while still achieving the sprint goal
• D.Allow the team to continue with the sprint and address the vulnerability in a future sprint

Why A: Option A is correct because the project manager should first assess the impact of the security vulnerability on scope, schedule, and cost, then submit a change request to formally address the issue. Option B is incorrect because bypassing change control violates project governance, especially in a hybrid approach where change management processes are defined. Option C is incorrect because requiring overtime to achieve the sprint goal ignores the rework impact and could lead to burnout and quality issues. Option D is incorrect because delaying the fix leaves the vulnerability unaddressed, which is unacceptable for a critical security issue.

• ✓ A.Submit a change request to the change control board to evaluate the impact on the project.
• B.Add the feature to the product backlog for prioritization in a future sprint.
• C.Ask the team to implement the feature immediately since it won't affect the sprint goal.
• D.Allow the product owner to approve the change since it is within the sprint.

Why A: In a hybrid project, scope changes, even if seemingly minor and within the current sprint, must be formally evaluated to understand their full impact on project objectives, timeline, and budget. The first action should be to submit a change request to the change control board (CCB) so that the potential change is analyzed properly. Option B is not the best first step because adding to the backlog without assessing impact could lead to scope creep or unintended consequences. Option C bypasses the formal process entirely, risking project misalignment. Option D is incorrect because the product owner cannot unilaterally approve scope changes without CCB oversight, especially in a hybrid framework where change control is still required.

• A.Ask the team to start working on the new feature immediately to meet the stakeholder's needs
• ✓ B.Submit a change request through the Integrated Change Control process to assess the impact on scope, schedule, cost, and quality
• C.Explain that no changes can be made after the sprint review to maintain the schedule
• D.Add the feature to the backlog and prioritize it for the next release without further analysis

Why B: The correct answer is B because any change that impacts scope, schedule, or cost must first go through Integrated Change Control (ICC) to assess its impact before approval. This aligns with PMI's change management best practices. Option A bypasses formal control, Option C is too rigid for a hybrid approach, and Option D delays analysis but does not initiate proper governance.

• A.Refuse the change because the scope was already agreed upon during sprint planning.
• B.Ask the team to include the new feature in the next sprint since it's a high priority for the stakeholder.
• C.Advise the stakeholder to wait until the project is complete and then submit an enhancement request.
• ✓ D.Submit a change request to the change control board for evaluation and approval.

Why D: In a hybrid project, changes are managed through a formal change control process. The stakeholder's request for a new feature is a significant change that must be evaluated for impact on scope, schedule, and budget before any action is taken. Submitting a change request to the change control board (CCB) ensures proper governance and prevents unauthorized scope creep, which is critical when the team has already begun planning the next sprint.

• A.Add the change to the product backlog for a future sprint without formal approval
• ✓ B.Submit a change request and evaluate the impact on the project constraints
• C.Instruct the team to implement the change immediately to maintain stakeholder satisfaction
• D.Reject the change because the feature was already accepted

Why B: In a hybrid project, changes to accepted deliverables must follow a formal change control process. Submitting a change request (Option B) ensures the impact on the critical path, schedule, and budget is evaluated before any rework begins, aligning with the PMBOK Guide's guidance on integrated change control.

• A.Ask the product owner to formally document the agreement and add it to the backlog
• ✓ B.Stop work on the feature and initiate a change request through the change control process
• C.Allow the team member to continue since the product owner agreed
• D.Escalate to the project sponsor for a decision

Why B: In a hybrid project, scope changes must follow a formal change control process to maintain baseline integrity. The team member's informal agreement with the product owner bypasses this, risking scope creep and unapproved work. Stopping work and initiating a change request ensures proper evaluation of impact on schedule, budget, and sprint goals before proceeding.

• A.Refuse the request, as the scope was already finalized
• B.Ask the team to start working on the feature to keep the customer happy
• C.Add the feature to the product backlog and prioritize it for the next release
• ✓ D.Submit a change request and conduct an impact analysis

Why D: In a hybrid project, changes to scope must follow a formal change control process. Option D is correct because submitting a change request and conducting an impact analysis ensures the feature's effect on cost, schedule, and quality is evaluated before any action is taken, aligning with both predictive and agile governance.