Activity Prerequisites on the Gantt Chart

Sep 22
08:24

2010

Vik Tantry

Vik Tantry

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

Project managers sometimes utilize this type of dependency to impose just-in-time scheduling into the project.

mediaimage
Apart from limitations enforced by dates as well as other elements,Activity Prerequisites on the Gantt Chart Articles there are the normal interdependencies that project managers need to deal with in a project. As the project manager completes the WBS, he can spot the jobs usually are not all possible in parallel mode. The truth is, there can be not many situations that activities could be executed in parallel mode. A project plan will normally reflect more sequential tasks than parallel jobs. There are numerous reasons for that type of predicament. Resources might be passed from a single job to another making the activity reliant on the resource availability. You will find tasks which can be by default sequential and cannot be started before the finishing the last action. As an example, a roof can not be constructed on the building until the walls and foundations are in position. In that case, the resources necessary for roof construction may be used by other responsibilities until the time comes for that roof construction. Below are a few job dependencies you will note in the Gantt chart and the way to interpret them. Finish to start. When you have two tasks, such as "construct house" and "paint house", it isn't surprising that you simply cannot paint the home before the home is constructed. It is a typical task dependency and happens frequently inside project plan. Some project managers may contend they can start painting the home around the parts which are already built and need not wait for an entire house to become finished before starting the painting task. Some other project managers will persist the home ought to be entirely finished before doing the paint job. Some job dependencies can be arguable, and the final decision lies with the project manager, except if overruled by management and also the stakeholders. Start to start. In this instance, an extra task can not start off before the first task has also begun. Both tasks start concurrently. They are parallel since both duties are possible to start off at the same time but there's a requirement for the reason that the secondary task may not start off until the first task has started. For example, "concrete pouring" and "level concrete" are two individual actions, but leveling the concrete can't start until the concrete is poured. Once concrete pouring will begin, then leveling the concrete may start. The time for both jobs are separate and distinctive. Finish to finish. A second task, although began at during the same time as the first process, cannot be finished till the first task is done. When you have two tasks, "electrical wiring installation" and "inspect wiring", the latter can't be completed until the installing of the electrical wiring is performed. The inspection of the wiring can begin once installing the electrical wires starts off, but could only be concluded by a final inspection if your installing the electrical wiring is completed. Start to finish. The primary job is not able to be concluded prior to the event that the secondary process begins.  It decreases the chance of an activity being late. Any update on the progress about the successor process is not going to impact the scheduled dates of the predecessor activity. Managers utilize this strategy moderately because the notion is a bit hard to understand and could involve substantial questioning by the management.