When you’d need it

A date-based roadmap tells the story, but the team needs to know what can start only after something else is done. PERT turns the launch into tasks and dependencies.

Key decisions

• Tasks are named with durations because schedule risk comes from work size, not labels alone.
• Dependencies are explicit, so the reader can see why frontend waits on both design and backend.
• The launch event is last because it depends on both QA and marketing readiness.

When to copy vs. adapt

Use this for project planning, launch dependency mapping, and critical-path conversations. Use a timeline when communication is more important than dependency logic.