Atlas: how we run delivery.
Our own system for running a project. Every piece of work has an owner, a design approved by a person, checks it must pass, and a record.
Two questions every client should ask.
Is software written with AI tools safe to rely on?
Only if people stay in charge of it. In Atlas a person approves every design, and the checks each piece of work must pass are enforced by the system. They do not depend on anyone remembering to run them.
What happens if your engineer is unavailable?
The state of the work is held in records, not in a head. Anyone picking it up can see what was designed, what was approved, what has passed and what is still waiting.
Four things, for every piece of work.
An owner
Each piece of work belongs to someone. Nothing is everyone's job.
An approved design
The design is written down, and a person approves it before anything is built.
Checks it must pass
The work is not done until its checks pass. The system enforces that.
A record
What was decided, built and checked is kept, so the history of the project is there to read.
One board, in plain view.
The board is where a project's progress is kept. Alongside it you get a regular written report in plain English.
- Progress towards the release.
- What got in the way.
- What it has cost so far.
- The decisions that are waiting for a person.
In daily use, and still being built.
Atlas runs our own product development today, and we are still adding to it. It was designed from experience of enterprise programmes, and it is the system our client projects run on from here on.
We will add client case studies to this page as those projects complete.
Interested in Atlas for your own team?
Register your interest and we will tell you when Atlas opens to other teams. If you would like to see how it would run your project with us, say so and we will show you.
Register your interest →