Every project, regardless of its method or framework used, is exposed to change. It is imperative that project team members understand that the Scrum development processes are designed to embrace change. Organizations should try to maximize the benefits that arise from change and minimize any negative impacts through diligent change management processes in accordance with the principles of Scrum.
A primary principle of Scrum is its acknowledgement that a) business stakeholders (e.g., customers, users, and sponsors) change their minds about what they want and need throughout a project (sometimes referred to as “requirements churn”) and b) it is very difficult, if not impossible, for business stakeholders to define all requirements during project initiation.
Scrum projects welcome change by using short, iterative Sprints that incorporate customer feedback on each Sprint’s deliverables. This enables the customer to regularly interact with the Scrum Team members, view deliverables as they are ready, and change requirements if needed earlier in the Sprint.
Also, the portfolio or program management teams can respond to Change Requests pertaining to Scrum projects applicable at their level.