From the course: Applying Agile MoSCoW Prioritization

Unlock the full course today

Join today to access over 22,500 courses taught by industry experts or purchase this course individually.

Reasons for change

Reasons for change

From the course: Applying Agile MoSCoW Prioritization

Start my 1-month free trial

Reasons for change

- If only all projects were run in a perfect world, we could plan what we wanted to do, how much it would cost, when it would be delivered, and everything would go according to plan. However, this is not a perfect world, and the reality is that things change. Let's take a look at some of the reasons that may cause changes in the project environment. The most obvious one, of course, is the request from a customer to change some aspect of the project. For example, imagine you work in a theme park and your original requirement was to build a picnic area with an African animal theme. Central to that was to be a life-size statue of a giraffe, and now someone has asked you to add an elephant. This request will take time and cost money, and will need approval as it's a change in the high-level scope. Another reason for a change could be a product that has been created but fails when tested. Sometimes, the only way that this can be resolved is to change something to make it work and pass the…

Contents