The Brief
Fourteen months ago, we were approached by a South African provincial government department with a significant challenge: their compliance document management process was entirely manual, tracked via Excel and email, and creating serious audit risks.
They needed a production system in 16 weeks. Budget was fixed. And everything had to meet government security standards.
Why Government Projects Go Wrong
Most government software projects fail for the same reasons:
**Scope creep by committee** — too many stakeholders, no clear decision maker
**Over-engineering the MVP** — building all possible features before validating core ones
**Technology choices driven by procurement rather than fit**
**No iterative delivery** — waterfall planning that produces a 12-month delivery date
We've seen this pattern repeatedly. Our approach is deliberately different.
Our Approach: Constrained Agility
We proposed a fixed-scope, fixed-cost contract with three two-week sprint reviews with key stakeholders. This meant:
Technical Decisions
For a government deployment, our non-negotiables were:
Security first:
Infrastructure:
Stack:
The Outcome
We delivered on day 108 of the 112-day project. All acceptance tests passed. The system went live with zero critical security incidents. Compliance submission rates moved from approximately 61% to 97.3% within the first quarter.
The lesson: government software doesn't have to be slow or expensive. It requires discipline, clear scope, and a team that has done it before.
Part of the Keystone Software team, building premium software for South African businesses.