Orangescrum
Documentation index for AI agents (llms.txt). A markdown version of this page is available at /critical-path-optimization.md or by requesting this URL with the header Accept: text/markdown.
Planning technique

Critical Path Optimisation, Explained Properly

Most projects are late because of a handful of tasks, not all of them. Here is how to find that chain, shorten it sensibly, and what Orangescrum shows you while you do it.

Start free trial See all features

What is critical path optimisation?

The critical path is the longest chain of dependent tasks in a project. Its length is your shortest possible finish, so any delay on that chain delays the whole project, while a delay elsewhere is usually absorbed by slack. Critical path optimisation means deliberately shortening that chain, either by doing tasks on it faster, by starting some of them earlier in parallel, or by removing a dependency that was never really needed. Orangescrum calculates and highlights the critical path on the Gantt chart, so you can see which tasks are on it and which have room to move.

Why the wrong tasks get the attention

  • Everything is treated as urgentWhen no chain is identified, every late task gets escalated equally. Effort goes into work that had two weeks of slack while the task that actually sets the date is left alone.
  • The dependency list is fictionHalf the links in the plan are habit rather than constraint. A critical path built on invented dependencies points at the wrong chain, confidently.
  • Shortening one task moves the problemYou compress a task, the chain shifts, and a different sequence becomes critical. Teams that only look at the path once end up optimising something that stopped mattering days ago.
  • Adding people is assumed to helpExtra hands shorten some tasks and lengthen others through handover and review. Without capacity in view, crashing a task quietly creates an overload somewhere else.

What Orangescrum actually gives you

Real features, named. Nothing here is an algorithm that decides for you.

See the critical path itselfThe Gantt chart works out the longest dependent chain and highlights it, so the tasks that decide your finish date are visible instead of guessed at.Critical pathRecord the real dependenciesLink only the tasks that genuinely block each other. The path is only as honest as the links behind it, so this is where the work actually is.Task dependenciesTest a change before you commitDrag a task on the timeline and everything downstream moves with it, so you can see whether a proposed reorder helps the end date or just looks busy.Gantt chartCheck who would carry the extra workBefore crashing a task, look at whether the person you would add is already committed. A workload view shows the overload you are about to create.Workload managementAnchor the chain to real datesMilestones mark the checkpoints the path has to hit, so a slip is discussed against a date somebody agreed to rather than a feeling.MilestonesCompare the plan with what happenedBaseline against actuals shows where the chain drifted, which is the only way the next project inherits a better estimate than the last one.Reporting

How to shorten the chain

  1. Get the dependencies honest firstGo through the plan and ask of each link what would actually break if the two tasks ran together. Remove the ones that are only convention. This step changes the critical path more often than any other.
  2. Read the path, then read the slackNote which tasks are on the chain and, just as importantly, which are not. Work with slack is where you can safely take people from, and where extra pressure buys you nothing.
  3. Attack the longest tasks on the chainA week off a three week task on the path is worth more than a week off five short ones that are not. Look for tasks that are long because they were estimated lazily, not because they are genuinely large.
  4. Overlap only where rework is unlikelyStarting a task before its predecessor finishes, sometimes called fast-tracking, works when the inputs are stable and fails badly when they are not. Overlap the safe pairs and leave the volatile ones alone.
  5. Recalculate, because the path movesOnce you shorten the chain, another sequence becomes the longest one. Look again after every meaningful change, otherwise you are optimising last week's plan.

What Orangescrum does not do here

Orangescrum calculates and shows the critical path. It does not optimise it for you. There is no crashing algorithm that decides which tasks to add people to, no fast-tracking engine that works out which tasks can safely overlap, no resource levelling, and no scenario comparison that lets you score two plans side by side. It also does not tell you when a dependency is unnecessary, which is where most of the real gain sits. You reschedule on the Gantt chart, watch the highlighted chain change, and decide. Critical path is on the Cloud Premium plan and included in Self-Hosted. If you need probabilistic schedule modelling or true mathematical schedule compression, that is specialist scheduling software and you would run it alongside us.

Critical path optimisation <em>FAQ</em>

Does Orangescrum automatically optimise the critical path?
No. Orangescrum calculates the critical path and highlights it on the Gantt chart, but it will not shorten it for you. There is no crashing, fast-tracking, or levelling algorithm that reorganises the plan to pull the date in. It shows you which chain sets the date and you decide what to do about it.
Does Orangescrum have critical path analysis at all?
Yes, and this is the part that is a real feature rather than a technique. The Gantt chart works out the longest chain of dependent tasks and highlights it. It is available on the Cloud Premium plan and included in the Self-Hosted edition.
What is the difference between the critical path and just the important tasks?
Importance is a judgement, the critical path is arithmetic. It is whichever chain of dependent tasks is longest, so it decides the earliest possible finish. An important task with two weeks of slack can slip a day without moving the date. A dull task on the critical path cannot.
Why does the critical path keep changing?
Because it is a property of the current plan, not a fixed list. Shorten the chain and a different sequence becomes the longest one. That is expected, and it is why the path is worth re-reading after every significant reschedule rather than once at the start.
Can I compare two versions of the schedule?
Not as a formal side by side comparison. You can drag work on the Gantt chart and watch dependent tasks and the highlighted path react immediately, which is enough for most teams weighing up a couple of options, but there is no scenario modelling or saved what-if feature.
Does Orangescrum warn me if a task on the critical path is slipping?
It does not raise a specific critical path alert. What you get is the highlighted chain on the Gantt chart, due dates, milestones, and normal task notifications. Teams that want an early warning usually review the Gantt at a fixed point each week rather than waiting to be told.
Is critical path the same as critical chain?
No. Critical path is about task dependencies and duration. Critical chain, from the theory of constraints, also accounts for shared resources and pools the safety margin into buffers rather than padding each task. Orangescrum supports the critical path method. It does not implement buffer management.

See the chain that sets your date

Free 14 day trial, no credit card. Every plan includes unlimited users.

Start free trial

Related

Gantt chartDependencies, milestones, and critical pathMilestone and deadline optimisationMaking dates mean somethingTask duration optimisationEstimating and shortening the work itselfParallel task executionWhen work is only pretending to be parallel