Topic: Project PlanningName: Course: Date: Critical path in a projectBy using the knowledge of tracking the critical path in a project, the resources are always assigned to the critical tasks which are determined by the tasks that affects the project completion on a timely manner. 1. These are the sequences of tasks that has no slack, and hence endorse the successiful finish date of the project. All tasks found here are fully on the critical path and therefore refered to as the project’s critical tasks. 2. This is a sequence of tasks that do not drive the project’s finish date.
All of this tasks are not critical. 3. The total slack is the total ammount of time that this sequence of tasks can slip before affecting the finish day of the entire project. Critical tasksCritical tasks are tasks that cannot be delayed without affecting the successful finish of the project. In a project, the majority of tasks have a slack and therefore, their delay cannot delay the projects finishing date. A task becomes critical when it meets any one of the following conditions: Has got no slack. Has a Must Start on, or Must Finish On, date constraintMust have an as Late as Possible constraint in a project scheduled from a start date.
Must have an As Soon As Possible constraint in project scheduling a finish date. Must have a finish date that is the same as or beyond its deadline dates. Critical risksThe project defines critical risks as those tasks that have no slacks. However you can amend when a task changes to a critical state. Slacks are determined by the early finish and the late finishing dates of the scheduled tasks.
Early finish date is the most probable earliest date of task completion. ReferencesLockyer, K. G., & Lockyer, K. G. (1991). Critical path analysis and other project network techniques (5th ed. ). London: Pitman.