JSON Validator
Regex Tester
Password Generator
JWT Debugger
Base64 Tool
Color Palette
Text Diff
CRON Builder
UUID Generator
SQL Formatter
Mermaid Editor
Markdown Exporter
HTTP Composer
Browser Inspector
SAFe Release Gantt Planner
Plan releases the SAFe way — features, PIs, and the cross-team dependencies that make or break them.
Options
0 features 0 dependencies
PI
Iteration
Month
Frequently Asked Questions
Is this real SAFe?
It models the SAFe planning artifacts teams use — PIs, iterations, features, enablers, milestones, and a dependency/program board — without prescribing any single org's process. You can adapt it to any PI cadence.
Where is my data stored?
Entirely in your browser (localStorage). Nothing is uploaded to any server. Use Export JSON to back up or share a plan with team members who can then Import it.
How does it flag a dependency risk?
The planner computes an effectiveReady date from the dependency's readyDate (actual) or falls back to committedDate. If effectiveReady is later than neededBy, the dependency link turns amber and is counted as "at-risk" in the summary strip. If the consumer feature has already started and the dependency isn't ready, it counts as "blocked".
Can I share a plan with my ART?
Yes. Click Export to download the plan as a JSON file and send it to colleagues. They open the tool in their browser and click Import to load the exact same plan, including all teams, features, milestones, and dependencies.
Does it work offline?
Yes — once the page is loaded the tool runs fully in the browser with no server calls. All data stays local. Reload the page and your plan is restored from localStorage automatically.
SAFe Planning Artifacts
A Program Increment (PI) is the primary planning horizon in SAFe, typically 10 weeks long and composed of 5 two-week iterations. The last iteration is the IP (Innovation & Planning) sprint — marked with a purple background — used for PI planning, inspect & adapt workshops, and innovation time.
A Feature is a service or capability that delivers value to a user or customer, deliverable in a single PI. An Enabler Feature (marked [E]) supports the architectural runway — infrastructure, technical debt reduction, or exploration.
Milestones are fixed points in time: PI Planning, System Demo, I&A, Release, or custom. They appear as diamonds on the timeline.
Dependency Risk Model
A Dependency is a commitment from an external team (API, UX, data, infra) that your feature relies on. The planner tracks:
- neededBy — the date your feature needs the dependency to be ready
- committedDate — when the provider team committed to deliver
- readyDate — the actual date it became ready (set after the fact)
Risk logic: effectiveReady = readyDate ?? committedDate ?? null. If effectiveReady > neededBy, the dependency is at-risk. The arrow connecting the dependency ready date to the consumer feature start turns red.
Date-to-Pixel Math
The Gantt axis is anchored at the first day of the first PI. Each zoom level maps days to pixels: Day = 40 px/day, Week = 20 px/day, Iteration = 8 px/day, Month = 4 px/day, PI = 2 px/day. A feature bar's left edge is (startDate − axisStart) / 86 400 000 ms × dayWidth px and its width is (endDate − startDate) / 86 400 000 ms × dayWidth px.
Drag & Resize
Drag a feature bar left or right to shift its start and end dates. Drag the left or right edge handles to change only the start or end date. All dates snap to the nearest calendar day. The plan is auto-saved to localStorage within 500 ms of any change.