For Mkb
Start fast. Fixed steps.
- A clear scope
- A practical plan
- A decision, including not to build
You'll recognise this
You are building before you know what to build.
Scope, architecture and the return are still open. The sprint has already started.
The brief is not written down
What to build is still a conversation. The sprint starts on a guess.
The architecture is assumed
Systems, data and the people who use them are not mapped yet.
The return is still a hope
You cannot see what the work is worth before the cost is spent.
What we build
Know what to build before you build.
- 01
The work, on paper
Processes, systems and data, including the exceptions.
- 02
Architecture and a roadmap
Named before anyone writes code.
- 03
A case for each idea
What it changes in the work, and what it costs.
- 04
Also: do not build yet
If a simpler thing fits, or nothing should be built, that is the answer.
Blueprint
Blueprint
Scope before sprint one
Ready for a decision
- Operation mappedReady
- Architecture definedReady
- Return made testableReview
Why it matters
The decision is on the page before the cost is spent.
We name the cost and the change before a sprint starts. We do not publish a return we cannot stand behind.
01
A clear scope
What to build is on the page. The sprint does not start on a guess.
02
An architecture you can keep
The systems, the data and the people are named before anyone writes code.
03
The return, written down
You see what changes in the work, and what it costs, before you commit.
04
A decision, including not to build
If a simpler thing fits, or nothing should be built, that is the answer.
What it looks like
Screens from work that already runs.
Choose a screen. These are real products, with realistic data. Not a customer's data.
Fiducia Studio
A focused interface built around the work people need to finish.How we work
From the first conversation to a system that runs.
01
Introduction
You get a clear view of where the work is stuck, and whether we should build.
02
Discovery
You get the process, the systems and the exceptions, written down with the people who do the work.
03
Blueprint
You get the scope, the cost and what should change. Not building is a valid outcome.
04
Build in sprints
Each week you see something working. You can say what is off before the next sprint.
05
Live and care
You get a tested release, documentation and a named owner. We stay, or we hand it over.
For Mkb and enterprise
Twenty people, or two thousand.
For enterprise
Architecture and security.
- The people and systems involved
- Architecture, security and access
- A phased case for the investment
Questions
Before you decide.
No. Discovery decides what to build. A sprint starts after the scope, the architecture and the return are written down.
What changes in the work, and what it costs, before you commit. Not a percentage we cannot stand behind.
No. If a simpler thing fits, or the work should not be built, we say that.
The scope, the architecture and the return, written down. The same team can then build it.
