Skip to content

For Executives

You want one answer, fast: is the work on track, and can you say so out loud without it coming back to bite you? You don’t operate the tool day to day — you need numbers you can trust and a forecast honest enough to admit its own uncertainty. This guide covers what TruePPM gives you today, stated plainly, and what’s still on the way.

Unlike traditional tools that show a single “planned finish date,” TruePPM’s Monte Carlo simulation produces probability distributions:

MetricMeaning
P5050% chance of hitting this date — where most tools stop
P8080% chance — the date your team should commit to
P9595% chance — contractual buffer

This is available today, per project, via the scheduling engine and API. Your project managers can run Monte Carlo on any project with three-point estimates.

The number you repeat to the board is only as good as the data under it. TruePPM enforces a five-role permission model on every project, so people see and change only what their role allows — and it’s enforced in the engine, not just hidden in the screen. You can be added as a read-only Viewer on any project to watch the live picture without being able to change it. (The PMO directors guide and the RBAC reference have the full role model.)

TruePPM runs on your infrastructure. No data leaves your network. The community edition supports:

  • PostgreSQL for data storage (standard backup/recovery)
  • Valkey (Redis-compatible) for real-time messaging (stateless, no persistent data)
  • JWT authentication with configurable token lifetimes
  • Helm chart for Kubernetes deployment

The REST API provides full access to all project data — tasks, schedules, CPM fields, members, resources. If your BI team needs to pull schedule data into a dashboard, the OpenAPI schema documents every endpoint.

The features most relevant to an executive sponsor are split across the community and enterprise roadmaps:

FeatureDescriptionEdition
Portfolio dashboardHealth scores, RAG status across all projectsEnterprise
Demand intakePrioritization workspace for project proposalsEnterprise
Cross-program coordinationDependencies and alignment across multiple programsEnterprise
Schedule forensicsNarrative detection of what changed and whyEnterprise
Basic single sign-onOIDC/OAuth login against your own identity provider (lands 0.4)Community (planned)
Org identity governanceSAML 2.0 federation, SCIM provisioning, LDAP/AD directory sync, enforced org-wide SSOEnterprise
Immutable audit trailCompliance-ready change historyEnterprise
Board-ready exportsClient-ready Gantt PDF (planned 0.4) and the reporting suite (planned 0.8)Community (planned)
Email/Slack notificationsEvent notifications by email and Slack webhook shipped in 0.2; a single-program health digest is planned for 0.8Community
Portfolio digestsProactive risk alerts and status summaries across the portfolioEnterprise

Evaluate it yourself (~5 minutes, no login of your own)

Section titled “Evaluate it yourself (~5 minutes, no login of your own)”

You don’t need to learn the tool to judge it — and you shouldn’t have to. Hand this section to whoever set up the demo, sit next to them or have them screen-share, and watch.

They run the setup:

  1. Start the stack and seed the demo. From the TruePPM checkout:

    Terminal window
    make up
    docker compose exec api python manage.py seed_demo_project --with-personas

    The command prints the persona logins and their shared password when it finishes. On a local Docker stack (DEBUG=True) that password is demo; anywhere else it is $TRUEPPM_DEMO_PASSWORD if set, otherwise a random token printed once.

  2. They sign in as the PM. At http://localhost:5173, as raj — the project-manager persona, seeded with the Scheduler role.

Then you watch three things:

  1. The forecast. They open Plan → Schedule in the left navigation rail. The Forecast bar docked along the bottom is the answer: it reads as a range with a confidence level — P50 ≤ P80 ≤ P95 — not a flat “on track / off track.” A forecast that won’t admit uncertainty is the one that embarrasses you later.

  2. Where it came from. Ask the one question: did anyone build this by hand? No — press Details › and the tornado names the specific tasks and risks driving the spread, computed from the live plan. That’s the whole difference from the two-day Excel ritual.

  3. The date you’d actually quote. P80 is the defensible number to take to the board; P50 is the optimistic one most tools show as “the date.”

Then judge it the way you actually decide. The technology is open and self-hosted, so your data never leaves your network. The two things you’d most want next — a one-glance portfolio dashboard and a weekly risk digest pushed to your inbox — are honestly still ahead (see “What’s coming”); the portfolio view is an enterprise capability, and a single-program health digest is planned for 0.8. If either is a dealbreaker for you today, that’s a fair call to make now rather than after rollout.

For the deeper architecture and roadmap behind a buying decision, see the architecture overview and the roadmap.