The Critical Path Method (CPM) models a project as a network of dependent activities and computes the longest path through it. That path is "critical" because any delay on it delays the whole project, while tasks off the path have float (slack).
CPM tells the project manager exactly which tasks to protect and where compression effort pays off. It underlies Gantt chart scheduling and pairs with PERT for handling duration uncertainty.
Example. Tasks A (3 days) and B (5 days) can start together; C (4 days) needs A; D (2 days) needs both B and C. Paths: A-C-D = 3 + 4 + 2 = 9 days, B-D = 5 + 2 = 7 days. The critical path is A-C-D and the project takes 9 days. B has 2 days of float, so it can slip 2 days before anything moves. Shortening B does nothing; shortening A, C or D shortens the project.
The forward pass gives each task its earliest start and finish, the backward pass its latest start and finish, and float is the difference. Keep the network honest by updating actuals weekly; the critical path changes when a task with float slips past it. The CPM guide works a larger network and the PERT guide adds three-point durations.