Your organization is implementing a new enterprise software system using a hybrid approach. The infrastructure setup and data migration follow a predictive waterfall model, while feature configuration and user acceptance testing use iterative cycles. You've just completed the second iteration of user testing when stakeholders request a major change to the data migration strategy that would affect already-configured features. The change would improve data quality but requires re-work of completed iterations. How should you handle this request?

Question

Accepted Answer

The correct answer is A. In hybrid projects, changes that span both predictive and iterative components require careful analysis of cross-component impacts. Conducting a thorough impact analysis and presenting options with clear trade-offs enables informed decision-making by stakeholders, which is essential for integrated change control. This approach honors both the change control rigor needed in predictive work and the adaptability of iterative approaches. Option C is the main distractor but is insufficient because this change affects the predictive baseline (data migration strategy), not just iterative scope, so it requires formal change control processes beyond backlog management. Simply adding it to the backlog doesn't address the impact on completed work or the predictive component.

More Process Questions