Menu
Why Way of Working Features Scenario Analysis Planning game Pricing
Do the challenge: 15 minutes

Welcome to the
Dependency Challenge

Can you plan the work across teams without violating dependencies?

📋 Project Status
🔴 Team Red Must work on Feature A (6 wks, ⭐13), then Feature B (4 wks, ⭐8), and Feature C (4 wks, ⭐5). 🔗 Feature A can only start after Team Blue finishes their Feature A.
🔵 Team Blue Works on Feature A (4 wks, ⭐13). Then Feature D (2 wks, ⭐2). 🔗 Feature D is a prerequisite for Feature C.
🟡 Team Yellow Has been working on Feature D (⭐2) for 4 weeks and needs 12 more weeks to complete. Total: 16 weeks.
🟢 Team Green Works on Feature C (2 wks, ⭐5), Feature A (4 wks, ⭐13) once Red is done, Feature B (4 wks, ⭐8), and Feature E (6 wks, ⭐8).

📏 Game Rules

  • Teams work in 2-week sprints
  • Each team has 4 FTE
  • Each feature requires the whole team
  • Teams can only work on 1 feature at a time
🗓️ Schedule the work in sprints
0:00
Team
S1
S2
S3
S4
S5
S6
S7
S8
S9
S10
Red
Blue
Yellow
Green
📦 Features to schedule (drag to sprint)
Taskstreamer calculating...
Analyzing dependencies
⚡

Solved in 52ms

All dependencies automatically resolved.

—
Your Time
52ms
Taskstreamer
Start Free Trial →

Now imagine doing this with 200+ features

Real product roadmaps have hundreds of features, dozens of teams, and dependencies that change daily. Manual planning doesn't scale.

🚨

Breaking News: New High-Priority Item Just Dropped

The CEO just came back from a customer meeting. There's a new urgent feature that needs to ship in 4 weeks.

📋

Manual Replanning

  • 2+ hours Gather all team leads for emergency meeting
  • 1+ hour Figure out which team can take this
  • 2+ hours Identify what gets pushed back
  • 1+ hour Check for broken dependencies
  • 1+ hour Update all the spreadsheets and slides
  • 30+ min Communicate changes to stakeholders
Total disruption: 8+ hours
...and you still might have missed a dependency conflict that surfaces next week.
VS
⚡

With Taskstreamer

  • 1 Add the new feature
  • 2 Set priority to "Urgent"
  • 3 Automatically recalculated
Entire roadmap updated
Total time: 42ms
All dependencies automatically respected. All teams see updated timelines instantly.
📊

Priority changes happen 3-5 times per week in most product organizations. That's 24-40 hours of replanning every month—or about €5,000+ in lost productivity for a typical team.

Stop replanning. Start shipping.

Let Taskstreamer handle the scheduling math so you can focus on building great products.

Explore Taskstreamer Features →