PI Planning & ART Simulator

Explore how cross-team dependencies, 100% utilization, and hidden constraints collapse the Program Board.

Features Committed
{{ committedFeaturesCount }}
Features Delivered
{{ completedFeaturesCount }}
Features Blocked
{{ blockedFeaturesCount }}
Feature Spillover
{{ spilloverCount }}
Points Lost to Variance
{{ Math.floor(state.capacityLostToVariance) }}
Points Lost to Dependencies
{{ Math.floor(state.capacityLostToDependencies) }}

ART Program Board ⚠️ Reduced Capacity Active

{{ feat.id }} | {{ Math.floor((feat.progress / feat.size) * 100) }}% 🔥
Teams
Sprint {{ iter }} (IP)
Planned
In Progress
Blocked (Dependency)
Delivered
Unplanned Work
System Dynamics: Business value is measured in Features, but Teams execute the underlying Stories. If a single Story has a red dependency badge, it blocks that item and puts the parent Feature at risk. Additionally, every dependency link adds a 15% coordination tax to the effort required for both the dependent and dependee stories, simulating the burden of cross-team alignment. If a team's planned work exceeds their daily capacity, unfinished Stories Spill Over (shift right) into the next sprint, cascading delays and destroying predictability.

Feature Backlog

Edit the features you want to plan for this PI.
ID Name Size (Pts) Act
{{ feat.id }} {{ feat.stories.reduce((sum, s) => sum + s.size, 0) }}
↳ {{ story.id }}
Note: Features exceeding ART capacity will be truncated.

PI Planning & ART Simulator

Welcome! This simulation models the execution phase of a PI (Program Increment). It illustrates how cross-team dependencies, high utilization, and hidden constraints can collapse a Program Board.

What this illustrates

  • The 100% Utilization Trap: Planning teams to maximum capacity leaves no slack for natural variance, guaranteeing spillover.
  • The Dependency Web: Cross-team links act as a "coordination tax" on both dependent and dependee teams, drastically inflating the effort required.
  • The Chaos of Unplanned Work: Injecting mid-PI defects steals capacity and cascades delays across committed features.

How to use the simulator

  • Select Scenarios: Choose a planning scenario like "The Dependency Web" to set up the board conditions.
  • Manage Features: Edit the backlog or add teams to see how capacity affects the plan.
  • Execute: Press Play to simulate daily execution and watch for blocked stories, missed iterations, and dropping predictability scores.