Parallel vs Sequential Work
You'll learn: How to analyze task dependencies to unlock concurrent progress and identify the critical path that determines your project's minimum timeline.
Understanding Dependencies
Not all tasks must be done in order. Some can run at the same time (parallel), while others must wait for predecessors to finish (sequential). The key is understanding dependencies—what blocks what.
Imagine building a house: you can't put on the roof before the walls are up (sequential), but you can have one crew working on plumbing while another does electrical (parallel). Software projects work the same way.
Finding Opportunities for Concurrent Work
When decomposing features into tasks (from earlier lessons), ask: "Does Task B actually need Task A to finish?" If not, they can run concurrently. Multiple engineers can work simultaneously, accelerating delivery.
Common parallel opportunities:
- Frontend and backend development (if API contract is agreed upon)
- Writing tests while another engineer builds the feature
- Documentation and implementation
- Multiple independent features in the same sprint
The Critical Path
The critical path is the longest chain of dependent tasks—the minimum time your project will take even with infinite engineers. You can't parallelize it away.
If Task A → Task B → Task C takes 6 days total, but Task D (independent, 2 days) runs alongside them, your critical path is 6 days. Adding more people to Task D won't speed up the project.
Identifying the critical path helps you focus optimization efforts where they matter and set realistic expectations.
Key Takeaway: Analyze dependencies to distinguish what must be sequential from what can be parallel—this reveals both acceleration opportunities and the critical path that defines your minimum timeline.