From the course: Applying Agile MoSCoW Prioritization

Unlock the full course today

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

Effect on prioritization

Effect on prioritization

From the course: Applying Agile MoSCoW Prioritization

Start my 1-month free trial

Effect on prioritization

- When changes occur on the project, that can have a big impact on the prioritization of requirements. In this video, we'll take a look at how this impacts the existing prioritization of the requirements, and what you will have to do with prioritization after a change has occurred. Consider an example when someone has asked for something new to be included in the project scope. Let's take an example of a new website for a theme park. We've been asked to add a new downloadable app to enable ticket bookings. This is a new requirement and the customer has informed us it's a must-have. This is a change to the original high-level requirement scope by adding in a totally new feature. The impact is that it will take time, cost money, and use resources that we probably don't have available. In Agile projects, change is expected and indeed embraced. So to now include this requirement will have a knock-on effect on all the other requirements and their priority. But this is why we use MoSCoW, so…

Contents