Case Study on Critical Path Method

Case Study about Critical Path Method

Planning a project usually involves dividing it into a number of small tasks that can be assigned to individuals or teams. The project’s schedule depends on the duration of these tasks and the sequence in which they are arranged. This sequence can be driven by several factors: customer deadlines, availability of personnel or resources, and dependencies among tasks. The last factor is the subject of this paper—in particular, how this sequence can affect the project’s duration and its finish date.



Case Studies on Critical Path Method

A schedule isn’t an arbitrary sequence of tasks, and it isn’t just a convenient arrangement that maximizes the use of resources for the shortest timeline. It must consider precedence—the relationship between the start and finish dates of interdependent tasks, where one task can’t start until one or more other tasks are finished. These precedence relationships determine which tasks can be overlapped and which ones must be serial. The purpose of any schedule is to define when tasks will begin and finish, but it’s important to remember that the purpose of project is not merely to perform tasks but to deliver a product.

Click here to read more on Critical Path Method


Comments

Filed under Change Management, Concepts