Catch delivery failure before schedules break.

Plan · Monitor · Forecast

Tracks demand vs. capacity over time — so you see overload coming before it arrives. Forecast accurately.

Built for the delivery lead who's tired of saying "we'll see" when stakeholders want a real date.

Will we deliver on time?
Who's overloaded?
Where's scope creeping?
What needs fixing now?
Jira Cloud
Dashboard Gadget
Jira App

Scrum or hybrid · Story points or time estimates

Get it on the Atlassian Marketplace Try it Live →

Most tools tell you what's happening. Project Commander helps you plan the work, monitor for problems as they emerge, and forecast delivery with confidence — for one project or for every project your team runs.

Without Project Commander
  • Find out you're late only when the deadline arrives
  • Scope creeps in and nobody notices
  • "Will we make it?" — "I think so"
With Project Commander
  • See the slip coming weeks before the deadline
  • Know exactly where and when scope grew
  • "Will we make it?" — "85% chance by March 15"

Built for project managers, scrum masters, and engineering leads who need to answer hard questions about delivery — not just track tickets.

See Project Commander in 30 seconds — turn sound on.

Start with the answer — Forecast

The question you came for is "will we hit the date?" So that's where the product starts. Open the dashboard and get the answer in one screen — then keep reading to see what keeps that answer true.

You committed to a date.
Is it still realistic?

Four stat cards — On Pace?, Delivery Forecast, Target Date, Progress — answer the question at a glance. Below them, a Delivery Forecast grid crosses every capacity model (Sprint capacity, Effective capacity, Team capacity, Velocity) with all four demand models (Ignore dependencies, Respect dependencies, Resequence work, Critical Chain only), giving a finish date and on-target odds for every combination — plus a Critical Chain floor for the earliest the work could possibly finish. Baselines snapshot the plan and track how the date drifts over time, and a Project Statistics table covers the risk factors behind it.

No digging through boards, no guessing. Open the dashboard, get the answer.

Dashboard: the four stat cards — On Pace?, Delivery Forecast (Oct 16, 2026, 40 days early, 96% on target), Target Date (Nov 25, 2026), Progress (57%) — above the expanded Delivery Forecast grid, with capacity models (Sprint, Effective, Team, Velocity) as rows against demand models (Ignore dependencies, Respect dependencies, Resequence work, Critical Chain only) as columns, each cell a finish date and on-target odds shaded green, amber, or red, and the Critical Chain floor flagged Earliest

See the impact before
you make the call.

The What-If tab lets you move sliders for velocity, scope, capacity, and estimation accuracy and see your delivery date shift in real time. Push scope up 20% — the cascade chart shows exactly which sprints absorb the overflow. Switch to Simulation mode and run a Monte Carlo analysis: instead of a single date, you get a probability curve. "We'll finish by March 15" becomes "85% chance we finish by March 15" — a number worth putting in a status update.

What-If tab: velocity and scope sliders, cascade chart, Monte Carlo probability forecast

Why the number holds up

Three reasons you can put this forecast in a status report where spreadsheets and gut-feel don't belong.

Auditable math, optional AI

The forecast itself runs on deterministic algorithms you can audit. AI is optional and is used for narrative summaries, risk suggestions, and translating natural-language scenarios into simulator adjustments — never as the source of truth for the math.

Real probability, not a guess

Monte Carlo simulation runs the forecast many times to give a likely-finish range and on-target odds, not a single optimistic line.

Uses your Jira data

Sprints, capacity, dependencies, history, time off, holidays. No second tool, no manual sync.

What keeps it true — Plan

The forecast is only as trustworthy as the plan and the capacity it reads. So before it gives you a date, Project Commander makes both honest — every sprint shows Deliverable or Overcommitted at a glance, Auto-Level rebalances overload in one click, and Team & Capacity tracks who can actually take on more.

Sprint 7 is overcommitted.
Sprint 8 is even worse.

Open the Sprints tab and every sprint shows a Deliverable or Overcommitted badge at a glance — with demand, capacity, and scope change on the same line. When one sprint is overloaded and another has room, hit Auto-Level and the work redistributes automatically, respecting priorities, dependencies, and per-sprint limits. Don't like the result? Undo with one click.

Stop manually dragging issues between sprints for an hour every Monday.

Sprints tab: Sprint 5 Deliverable, Sprint 6 Deliverable, Sprint 7 Overcommitted, Sprint 8 Overcommitted — each with demand, capacity, and scope pts

Someone is underwater.
How much can your team take on?

The Team & Capacity tab shows every team member's demand vs capacity at a glance — who's overloaded, who has room, and by how much. Set weekly hours, mark time off, add holidays, and capacity updates everywhere automatically. Status badges (Optimal, Overloaded, Available) make imbalances obvious.

Running people across multiple projects? Each row's Alloc cell shows percent totals per unit (Hrs: X% / 100%, Pts: Y% / 100%) and opens a popover where you edit each project's allocation as a percent of capacity, with an editable “= X” computed value next to it, labelled per period (pts/sprint or h/wk). Bump someone's Pts/Wk and every “= X” updates live — a 60% allocation stays 60% across capacity changes.

Stop burning out your best people. Capacity planning that accounts for real life.

Team & Capacity tab: per-member rows with weekly capacity, utilisation, the Alloc column showing percent totals per unit, time-off deductions, and status badges
What keeps it true — Monitor

Once the plan is sound, two things quietly break it: scope creeping in and capacity slipping out. Project Commander watches both — rebuilding scope history from your Jira changelog so you see exactly when work started running ahead of plan, and testing week by week whether your capacity can still absorb the work on the books.

Scope keeps growing.
Nobody sees it happening.

The Scope tab rebuilds scope history from Jira changelogs and renders burndown and burnup on the same chart: Ideal Burndown, Remaining, Scope, Forecast, plus Burnup, Ideal Burnup, and Burnup Forecast. Read progress as work remaining or work completed — whichever framing your team uses. Filter by team member, switch between Weekly, Monthly, Quarterly, or Sprint-bucketed views. The "Now" marker separates history from forecast so you can see exactly when scope started running ahead of plan.

Below the timeline, the collapsible Demand vs Capacity chart tests feasibility week by week — whether the team's available capacity can absorb the demand on the books. A cumulative over-by headline calls out infeasible periods; hover any week for the weekly capacity, demand, scope, completion, and overload breakdown.

Scope creep is the silent project killer. Now it's visible.

Scope tab: Ideal Burndown, Remaining, Scope, and Forecast lines on a weekly chart with team member filter and Now marker Demand vs Capacity chart on the Scope tab: weekly capacity vs weekly demand across the project, with hover tooltip showing the weekly breakdown and overload amount
Run every project as one program

Running multiple projects?
See them all in one place.

Open the Projects tab to see every project's health, forecast, slack, utilization, and alerts in a single table. Switch the header selector to Program view and every tab — Dashboard, Scope, Alerts, Risks, Actions, Epics, Team & Capacity, What-If — rolls up across every project you manage. Register cross-project dependencies here too. The table is a read-only overview — to model program-level changes (adding people, scope, a slowdown) use the What-If tab's All Projects view.

The Team Allocation Matrix below the projects table splits each member across the program's projects: each cell shows the percent of that member's capacity dedicated to the project, paired with a “= X” computed value labelled per period (pts/sprint or h/wk). Σ percent totals per row flag over-allocation independently for hours and points. (Allocations are edited in the Team & Capacity tab's Alloc popover; here they're shown read-only.)

A critical chain diagram shows the resource-constrained path to delivery across all projects — which issue is blocking everything else, and who is the bottleneck.

Projects tab portfolio table: one row per project with health, progress, forecast, target, slack, scope, utilization, team, alerts, and estimation columns, and a Program rollup row at the bottom

Overview

Dashboard, Sprints, What-If, Team & Capacity, Scope, Alerts, and more.

See It in Action

Try it Live →

Interactive demo with sample data — no install required.

A Complete Toolkit — Plan, Monitor, Forecast

Everything you need to answer the hard delivery questions — in one app.

Plan
📋

Planning

Drag-and-drop issues between sprints, multi-select to move in bulk, and inline-edit Story Points, Original Estimate, Due Date, Assignee, Priority, or Summary right in the table. Toggle List View for a flat searchable view, or quick-filter inside any sprint. Per-sprint state-aware modes (Status while active, Retro once closed) plus a Risks button that surfaces AI-detected risk factors.

🔗

Dependency Tracking

Cross-sprint blocker detection, dependency map, and violation highlighting. Know which blockers will cascade before they do.

🏙

Program Management

Run multiple related projects as one program from the Projects tab: a read-only portfolio table (health, forecast, slack, utilization, alerts per project), cross-project dependencies, and a team allocation matrix showing each member's percent-of-capacity per project with a computed “= X pts/hrs” readout. Switch the header to "Program view" and every tab unions data across projects. Critical Chain shows the resource-constrained delivery path across the program. To model program-level what-if changes, use the What-If tab's All Projects view.

Monitor
🚨

Alerts

Issues that need attention grouped by domain (Risk strategy, Dependency risk, Data quality). Circular cycles include an inline recovery hint naming the edge to break; the overdue-blocker check flags blockers still open after the work they're blocking should have started. Severity pills, search, per-alert dismiss, and a Create risk shortcut on the dependency and data-quality category headers (and a per-alert Create action button).

☑

Risks & Actions

Live risk register split into AI Generated suggestions and Manually Entered risks. Probability × Impact with derived severity, RACI owners (A/R/C/I), and a response strategy chip on every risk (Avoid, Mitigate, Transfer, Accept, Escalate, Defer) with strategy-specific required fields and a full audit trail. Sprint-End Closure retires risks whose mitigation actions are all done. Actions render as cards with severity stripes, scope levels (program / project / sprint), originator, priority, and dated comments.

🎯

Epic Tracking

Single overview table with progress bars, point totals, assignee, dates, and Jira status. Sortable columns, search, and dynamic status filter. Expand any epic to see child issues.

Forecast
📅

Delivery Forecast

Delivery forecast with a choice of capacity models (sprint capacity, team capacity, effective capacity, velocity). An optional per-user breakdown stacks the cascade bars by assignee to show who is over capacity and when. Auto-Level surfaces P50/P85 finish dates from a Monte Carlo run on the resulting plan.

🔎

Impact Analysis

In the What-If tab's All Projects view, model adding people, a scope change, or a slowdown across the whole program: drag the capacity, scope, and velocity sliders and the rolled-up forecast, each project's date, and the on-target odds update live. Switch to Simulation and a Monte Carlo run turns gut feel into a probability curve and ranks which project is the weakest link — all without touching Jira.

📊

Capacity × Demand grid

Every capacity model (Sprint, Effective, Team, Velocity) against every demand model (ignore or respect dependencies, resequence work, the Critical Chain floor) in one grid on the Dashboard, Scope, and What-If — each cell its finish date, gap to target, and on-target odds. Click a square and the Delivery Forecast card reflects it.

📷

Baselines

Capture named snapshots of the plan and watch the forecast move over time. Each baseline is frozen — later changes never alter it — and a timeline plus table shows the slip against target, with a per-baseline breakdown on hover. Works per project and across a program.

See All Features with Screenshots

Plan Better. Ship on Time.

Install Project Commander on your Jira instance and start planning, monitoring, and forecasting in minutes — Auto-Level fixes overloaded sprints in one click, the Dashboard tells you if your deadline is still realistic, and What-If scenarios let you model any change before you make it. Works with sprints or kanban, points or time estimates. Writes back to Jira through your existing session, using your existing permissions.

Get it on the Atlassian Marketplace Try it Live →

Free during beta — no credit card, no commitment. Questions? support@projectcommander.app