Product Self-Hosted Docs View on GitLab Deploy self-hosted →
The product

Every view is the same truth.

Board, schedule, work breakdown, calendar, sprints, resources, risk — TruePPM derives them all from one set of tasks and dependencies. Change anything anywhere and the rest stays consistent, automatically.

Deploy self-hosted Tour the views
The TruePPM Schedule view in Grid layout: the WBS task list with dependency links, durations, dates, progress and owners beside the Gantt chart
One model, six views

Pick the surface, keep the truth.

Each view is a projection of the same underlying tasks and dependencies — never a separate copy to reconcile.

The Board view with the active sprint panel open above the phase columns

Board

Kanban swimlanes by phase, owner or sprint. Cards carry the same dates as the schedule.

The Schedule view in Timeline layout with the critical path and forecast bar

Schedule

A real timeline — the Gantt chart — with critical-path highlighting, slack (float), baselines and auto-leveling.

The Grid view in Outline mode: phases, owners, dates, durations and predecessors

Work breakdown

The hierarchical breakdown of work — also known as a WBS — with rollup of effort, cost and progress at every level.

The Calendar view in Month mode with task chips spanning working days

Calendar

Deadlines, milestones and capacity on a working calendar that respects holidays.

The Sprints page: goal, burndown, capacity preflight and velocity

Sprints

A real sprint container — goal, capacity, burndown, velocity with a forecast range — that reforecasts the program schedule on close.

The risk register: probability-by-impact heatmap beside the sortable risk table

Team & Risks

Resource allocation, over-capacity warnings, and a risk register tied to the schedule.


Agile ↔ Waterfall

The bridge isn't a compromise.

A board card and a timeline (Gantt) bar are two renderings of one task. Story points and day-durations stay reconciled. Teams that live in sprints and teams that live in schedules finally share a plan instead of arguing about two.

  • Points ↔ duration mapping per team
  • Sprint close advances the program schedule
  • Cross-team dependencies that actually hold
A hybrid project's Schedule: waterfall launch-planning tasks above a Scrum phase whose sprint windows are drawn on the Gantt chart
A hybrid project · phases and gates on top, a sprint phase inside them, one schedule
The bottom of a TruePPM schedule after a Monte Carlo run: the Forecast bar reads P50 Nov 30, P80 Dec 2 (+6d), P95 Dec 4, CPM Nov 26, and names the top driver
P50 / P80 / P95 beside the deterministic CPM date, and the task that moves it most
Probabilistic forecasting

Commit to a date you can defend.

Monte Carlo simulation runs the whole network thousands of times against your estimate ranges. You get P50/P80/P95 dates — the dates you're 50, 80, and 95% likely to hit — and a ranked list of the tasks that actually drive risk, so you know exactly where to buy schedule back.

Deploy self-hosted

See it on your own plan.

Import a project, derive the schedule, and read your first forecast in minutes.

Deploy self-hosted Read the docs