Critical Path Mode (CPM)

Rapids elevates standard Jira links into actionable project management insights using the industry-standard Critical Path Method (CPM).

What is the Critical Path?

The critical path represents the longest sequence of dependent tasks that dictate the overall duration of your project. It is the bottleneck of your schedule. If any task on the critical path is delayed, your entire project delivery is delayed. Conversely, expediting tasks on the critical path is the only way to shorten the overall project timeline.

Enabling Critical Path Mode

At the top of the Rapids interface, you will find the Critical Path Mode toggle. Turning this ON will instantly transform your dependency graph to highlight the critical sequence.

Critical Path Demo

Demo: Toggling Critical Path Mode to reveal the project’s bottleneck.

Interpreting the Visuals

When CPM is enabled, the graph intelligently re-renders:

Highlighted Paths: The critical path - and the specific issues that form it - are highlighted in a bold red/orange color.
Dimmed Paths: Non-critical paths and their associated issues are dimmed into the background. This visual contrast immediately draws your attention to what matters most.
Legend Panel: A legend will appear in the bottom-left corner of the screen, explaining the meaning of edge colors, node borders, and highlighting.

How it’s Computed

Rapids automatically calculates CPM metrics in real-time for every issue on the board, based on your estimations (Story Points or Man-Days) and issue links:

Early Start (ES) & Early Finish (EF): The earliest times a task can begin and end without violating dependencies.
Late Start (LS) & Late Finish (LF): The latest times a task can begin and end without delaying the project.
Slack (Float): The difference between the Early Start and Late Start. This represents the amount of time a task can be delayed without causing a delay to subsequent tasks or the project completion.

Tasks with zero slack are the ones highlighted as your critical path. By knowing exactly where your critical path lies, you can proactively reallocate resources or adjust scope before a sprint fails!