PERT, similar to the critical path, is a way to visualize the progress of project tasks within a project and estimate deadlines based on their estimated duration. This method also shows the interdependencies of tasks.
To create a project schedule using PERT, as with CPM, you first need to define tasks and their order based on the project's milestones. Using a CPM-like network system made up of these tasks, you can calculate different project deadlines depending on the level of confidence:
Optimistic time
Most likely time
Pessimistic time
Although PERT is very similar to CPM, PERT uses weighted ivory coast telegram phone numbers average duration rather than estimates to calculate possible deadlines.
A disadvantage of this method is also that to fully benefit from this method, you need to know all the tasks and their interdependencies.
Duration compression is a method of shortening a schedule. It can be useful if a project is running behind schedule and you need to find a way to adjust the schedule without changing the project scope. There are two methods you can use: fast-tracking and crashing .
2.1. Rapid monitoring
Since you already know what the critical path is, here's another way to use it. The critical path helps you find tasks that can be done simultaneously or overlap to speed up your project. To do this, look at the critical path and decide which activities could be accelerated.
Let's say you've started a new project and have already gathered all the requirements. At this point, you can start the design phase and only when the design is ready, start developing the software.
However, if you need to speed up both processes, you can start developing the software after the most important designs are ready first. Then continue to prepare subsequent images while the programmers implement the material already received.
Rapid planning is an example of a project planning method. While rapid planning may seem appealing, don't forget the risks. Because you'll be managing multiple important activities at once, it's easier to make costly mistakes or sacrifice quality.
2.2. Disturbed
Another way to squeeze is to add additional resources to complete the project on time. However, this is difficult because you need to have free resources that you can use.
Additionally, not all tasks can be completed faster with more team members. According to Brook's Law, "adding more human resources to a late software project makes it later," which is related to the general law of diminishing returns. This is due to the additional communication required to familiarize new team members with the project and the limited division of tasks.
Another way to use the collapse method is to add time (such as paid overtime), but it still has to meet the deadline. However, the disadvantage of this method is that it increases the cost of the project.