Scope Change Request in Hybrid Projects: The First Step

• A.Add the feature to the product backlog and prioritize it in the next sprint planning
• B.Inform the product owner that no changes can be made once the sprint has started
• ✓ C.Submit a change request to the change control board and assess impact on schedule, cost, and resources
• D.Ask the team to start working on the feature immediately to satisfy the stakeholder

Why C: According to PMI, any scope change must go through the change control process. The most appropriate first step is to document and assess the impact of the change.

• ✓ A.Submit a change request through the Integrated Change Control process
• B.Add the feature to the product backlog and prioritize it for a future sprint
• C.Ask the team to add the feature to the current sprint backlog to satisfy the product owner
• D.Tell the product owner that no changes are allowed after the sprint starts

Why A: The correct answer is to submit a change request through the Integrated Change Control process to formally evaluate the impact on scope, schedule, and cost before any work begins.

• ✓ A.Submit a change request through the Integrated Change Control process and assess the impact on scope, schedule, and cost
• B.Ask the team to start working on the feature immediately to satisfy the customer
• C.Inform the customer that the feature is out of scope and cannot be added
• D.Add the feature to the product backlog and schedule it for a future sprint without further analysis

Why A: The correct action is to submit a change request through the Integrated Change Control process. PMI requires formal assessment and approval before implementing any change that impacts scope, schedule, or cost. Proceeding without change control violates the project management plan.

• ✓ A.Document the request and submit a change request through the change control process
• B.Add the enhancements to the product backlog and prioritize them for the next sprint
• C.Instruct the team to begin work on the enhancements immediately to maintain customer satisfaction
• D.Thank the customer for the feedback and explain that the project scope is frozen

Why A: The correct first step is to document the customer's request and submit a formal change request through the established change control process (Option A). This ensures the impact on scope, schedule, and budget is properly assessed and approved before any work begins. Option B bypasses change control and could lead to scope creep. Option C is reactive and unsanctioned. Option D incorrectly closes the door on the request without allowing the customer to formally submit it, which could damage stakeholder relationships and ignore a valuable opportunity.

• ✓ A.Submit a change request to the change control board for evaluation and approval.
• B.Ask the team to implement the feature and document it as a scope change later.
• C.Inform the customer that no changes are allowed after the sprint review.
• D.Approve the request since it is small and won't affect the schedule.

Why A: According to PMI, any change to scope must go through the change control process. Even if the change seems small, it requires formal evaluation and approval to prevent scope creep and ensure all impacts are considered.

• A.Add the feature to the current sprint backlog immediately to not delay the release
• ✓ B.Submit a change request and evaluate the impact on the project constraints
• C.Tell the team to implement the feature during any free time
• ✓ D.Ask the product owner to prioritize the feature against existing backlog items for the next sprint
• E.Reject the request because it is outside the original scope

Why B: Options B and D are the correct next steps. Option B is correct because any change to scope outside the current iteration must go through a formal change control process to assess impact on constraints such as time, cost, and quality. Option D is correct because the product owner is responsible for prioritizing the backlog; the new feature should be evaluated against existing items for the next sprint to ensure value delivery. Option A is wrong because adding work to the current sprint without approval violates the change control process and disrupts the sprint commitment. Option C is wrong because using free time for unplanned work undermines transparency and may lead to scope creep without proper assessment. Option E is wrong because completely rejecting a potentially valuable feature without analysis is not agile; the product owner should decide based on priority and value.

• ✓ A.Ask the product owner to submit a change request for formal evaluation
• B.Add the feature to the sprint backlog and accept the change
• C.Reject the feature outright because it is not in scope
• D.Tell the team to work overtime to accommodate the feature

Why A: In a hybrid project management approach, changes to the approved product backlog must follow a formal change control process to maintain baseline integrity and avoid scope creep. Asking the product owner to submit a change request ensures the proposed feature is evaluated for impact on schedule, cost, and quality before any work begins, aligning with both agile principles of prioritization and traditional project governance.

• A.Refuse the request because the project is already on schedule and budget.
• B.Add the feature to the product backlog and prioritize it in the next sprint planning.
• C.Instruct the team to start working on the feature immediately to maintain stakeholder satisfaction.
• ✓ D.Submit a change request to the change control board for evaluation and approval.

Why D: In a hybrid project, the sprint review is a feedback session, not a change implementation point. The product owner's request is a change to the project scope, and the correct first step is to submit a formal change request to the change control board (CCB) for evaluation and approval, ensuring alignment with the project's governance and baseline.