Project compression is the same thing as schedule compression, and it is done by the project manager, after consulting with team members. Project compression is used to shorten the length of the project, without affecting the scope.
There are two ways to compress projects: Crashing and Fast Tracking.
Crashing is about either adding more resources to the project, or making the current resources work extra time. Crashing is usually associated with increased costs on the project.
Fast tracking, on the other hand, is about finding tasks that are scheduled to take place in the future, and make the resources work on them before that scheduled time. Naturally, these tasks cannot be dependent on other tasks that are not yet finished. Now the downside of fast tracking is that when resources work on tasks that they really shouldn't work on at the moment, risks of doing tasks the "wrong way" will definitely increase.
Note that crashing and fast tracking are not mutually exclusive, they can go hand in hand. You can add more resources to the project and do fast tracking.
The advantages of project (schedule) compression are:
- You will most likely finish faster
- Your stakeholders will be happy
The disadvantages are:
- You will probably only finish on time.
- Many tasks may need to be redone, especially when you're using fast tracking.
- Resources will be exhausted when you make them work over time.
- Costs will be higher (often much higher).
No comments:
Post a Comment