In this video, Claudine Peet describes the different impacts on the different levels of requirements and what changes can do to this. She also explains the impact on the breadth vs. depth of change and change control steps.
- When a change arises in the project,…whatever the circumstances, it will have an impact.…The way you make changes, will have been agreed upon…during the definition stage of the project,…and an escalation process will have been agreed upon…for any type of change.…In a project that's using MoSCoW prioritization…for its requirements, it's important to understand…what changes mean, and how they will impact the project.…Think of it as a sculpture project.…You're building a six foot giraffe, and partway through,…you're asked to add a four foot elephant and an enclosure.…
The first thing to do is to assess if the change…is at breadth or depth level.…A change to the project breadth means…something has been added to the high level requirements…for the project.…If a project was just to build a giraffe,…then you've added additional scope to your project…by adding in an elephant and an enclosure.…As this was not previously included,…it's considered a change to the breadth of scope.…As this change will impact the costs and the time scales…
- Describe what a project’s variables are.
- Identify the best time to define broad project requirements.
- Summarize the process of testing the requirements of a project.
- Recall tips for prioritizing requirements.
- Explain the process of making a requirement change.