If the Gantt Chart is the map, then Milestones and Dependencies are the terrain and the road rules. Without them, a project schedule is just a collection of disconnected bars. With them, it becomes a predictive engine that reveals the project's true heartbeat.
The Deep History
Network logic wasn't born in a board room; it was born in the Cold War. In the late 1950s, the U.S. Navy faced a massive challenge: building the Polaris Missile. With thousands of contractors and components, they needed a way to track how a delay in a tiny valve affected the final launch date. This led to the creation of PERT (Program Evaluation and Review Technique). Simultaneously, DuPont developed the Critical Path Method (CPM) to manage complex chemical plant maintenance. Both relied on the same fundamental principle: the logical relationship between tasks.
The Key Points of Network Logic
Understanding dependencies requires moving beyond "A then B." You must understand Float (Slack)—the breathing room in your schedule.
- Total Float: How much a task can be delayed without delaying the project finish date.
- Free Float: How much a task can be delayed without delaying the next task.
- The Critical Path: The chain of tasks with zero float. If any link breaks, the whole project slips.
Example: The Software Release Cycle
Imagine a standard SaaS feature release:
- Dependency (FS): You cannot Start QA until the Code Freeze is finished.
- Lag: You might add a 2-day Lag after Code Freeze for the environment build to stabilize.
- Milestone: "Production Push"—a zero-duration event at 12:00 AM on Friday.
Hidden Logic: If the API Documentation (Successor) depends on Backend Code (Predecessor) via an SS (Start-to-Start) relationship, the writer can start as soon as the developers start, which compresses the schedule.
The Traps & Hidden Hazards
PMs often create too many milestones (e.g., "50% Complete on Design"). When everything is a milestone, nothing is a milestone. The Trap: Diluting the significance of real delivery and creating reporting fatigue.
Classic PM tools often hide dependencies that aren't logical, but resource-based. The Trap: Task A and Task B aren't logically related, but they both need "John." If you don't link them, the tool assumes they run in parallel, creating an impossible schedule.
In complex projects, it's easy to accidentally link A → B → C → A. The Trap: The scheduling engine crashes because the math becomes impossible. This usually points to a fundamental misunderstanding of the workflow.
The Scrum Perspective: Flattening the Logic
Scrum "deprioritizes" complex dependency networks in favor of Speed and Flexibility. However, the logic remains hidden in different containers:
- The Sprint Boundary: A fixed milestone that forces the team to "Finish" or "Fail" within a cycle.
- The Sprint Review: A milestone for stakeholder alignment and feedback.
- External Dependencies: The biggest risk for Scrum teams. If a third-party API isn't ready, the Sprint Milestone is at risk. Scrum teams solve this during Refinement by making sure stories are "Ready" (no blockers) before pulling them into the Sprint.