Why replan? |
1. |
The original plan was incomplete or inadequate. |
2. |
The plan was not considered fully. It was merely a wish list. |
3. |
The project plan was not adhered to closely and was not updated. |
4. |
A basic assumption was wrong. |
5. |
The end-users say they no longer require the outputs. It can, for example, be too late to address the problem. |
|
Action steps |
1. |
Acknowledge that there is a problem. |
2. |
Determine the exact situation. |
3. |
Find out why it has happened. |
4. |
Agree on a solution which will put the deliverables and target dates back on track again. (Balance the triangle of deliverables, time and costs.) |
5. |
Follow the change control procedures. |
|
Potential solutions |
1. |
Reduce the scope |
|
Remove certain objectives or deliverables from the project (after consultation with the relevant roleplayers). |
2. |
Change the project structure |
|
- Is each task necessary? |
|
- Has each essential task been included? |
|
- Are all the dependencies still valid? |
|
- Can the tasks overlap? |
3. |
Reduce the duration of the tasks |
|
This often happens during the course of the project as more information becomes available. |
