Test
Project control software is only worth something if its figures are right and its vocabulary is that of the people who use it. Testers are the ones who check.
An online demo, as soon as accounts and access rights are delivered
As soon as EP-03 is delivered (accounts, authentication and access rights, currently in progress), a demonstration of Waterfall will go online. No installation: a browser is enough. It will grow with every delivered slice: reference data, projects and revisions, scheduling, costing, actual costs, indicators, risks, portfolio (see the roadmap).
A reference walkthrough: your data stays with you
The demo comes with a reference walkthrough that covers the business situations to be put to the test. You do not need to bring any data or files from your organisation: just follow the walkthrough and tell us what you think. What interests us:
- what blocks you, surprises you or needs explaining along the way;
- vocabulary that sounds wrong, or that is not used in your trade;
- a figure that does not look consistent with the rest;
- what is missing to prepare a project review or a steering committee.
To be told when the demo opens, write to us. Defects are then reported through a GitHub issue, in English or in French.
Meanwhile: the mockup
The mockup already shows every screen, wired to a fake service that serves the API contract’s examples. If you are comfortable with development tools, you can run it on your machine from the repository (make dev, with Docker, Node 24 and uv).
Review the specification
Project manager, cost controller, PMO, bid manager: you know the situations the specification must cover. In more than two hundred requirements it describes how Waterfall handles an amendment, a provision, unanticipated work, an ERP extract. Your reading is one of the most useful contributions there is: a rule that does not hold against a real case is cheap to fix in a document and expensive to fix in code.
A few questions that deserve a practitioner’s eye:
- Does the way you handle amendments fit the model of a baseline budget that only moves by contract?
- Are your risk provisions managed as a reserve kept outside the budget?
- Does the 0/100 rule of earned value suit the length of your tasks?
- Do your ERP cost assignment codes allow reconciliation per sub-project?
The specification is written in French. A remark takes the form of a finding: the place concerned (a section or a requirement identifier), an exact quotation and a proposed wording. The reviews already carried out show what this looks like. If the format puts you off, a plain description of the case is enough to start: write to us, in English if you prefer.
Develop
The service is written in Python (FastAPI), the interface in TypeScript (Next.js), on PostgreSQL. The API contract is authoritative, and work arrives in batches reviewed and checked by the CI chain. The contribution guide sets out the rules, and the open source page presents the repository and the technical stack.
A feature idea first goes through the “Question or proposal” issue template: it becomes a user story when it enters an epic.
Spread the word
A star on the GitHub repository, a message to a cost controller colleague, a link to these pages from a project management course: a free software project also lives through the people who talk about it.