Step‑by‑step guide to rescuing stalled government digital transformation projects

Rescuing a Stalled Government Digital Transformation Project

1. Secure the engagement and protect data

Before any technical work begins, sign an NDA that matches the legal team’s preferred template. This satisfies procurement rules and lets you exchange system diagrams, database dumps and credential files.

2. Conduct a rapid audit (Project Restoration)

Gather all artefacts, source repositories, CI/CD pipelines, infrastructure as code, and runbooks.

• Identify which environments are still reachable (Docker containers, Kubernetes clusters, on‑prem VMs).
• List integration contracts (payment gateways, third‑party APIs).
• Flag missing documentation or orphaned services.

The audit produces a baseline health report that shows where the project stalled: missing migrations, broken CI pipelines, or undocumented secrets.

3. Map the existing ecosystem (Discovery)

Run a focused discovery session with the engineers who will do the work. Produce three deliverables:

1. System map, a diagram of all applications, data flows and integration points.
2. Agreed objectives, specific outcomes the restored system must achieve (e.g., “process 10 000 reimbursements per day”).
3. Fit assessment, a technical and operational view of whether the current stack can meet the objectives.

A clear map prevents later “we didn’t know about that system” surprises.

4. Validate risky assumptions with a proof‑of‑concept

If the proposal depends on an unproven component (e.g., a custom payment callback, a legacy data migration), build a small proof‑of‑concept in an isolated environment. This step keeps the overall timeline and budget predictable, as highlighted in Afriq Silicon’s process.

5. Refine scope, timeline and budget

Using the audit and PoC results, draft a written proposal that spells out:

• What the restored system will and will not do.
• The architecture and the reasoning for the chosen stack, including Docker for packaging and Pulumi for infrastructure as code.
• A milestone‑driven timeline broken into two‑week increments.
• A cost breakdown that aligns with the client’s approval limits.

Iterate until the scope matches the budget; prioritize core functionality first and plan phased enhancements for later.

6. Formalise the contract and milestone map

Rewrite the proposal as a binding contract that mirrors the agreed scope. Then create a milestone map: each two‑week sprint has a clearly defined deliverable, demo date and payment trigger. This gives the client confidence that “what should exist by when” is documented from day 1.

7. Re‑engineer the infrastructure (System Orchestration)

Before the first feature lands, stand up the target environment:

• Use Docker for packaging and Pulumi for infrastructure as code.
• Deploy a CI pipeline with GitHub Actions to run tests, linting and automated builds.
• Set up monitoring and security hardening such as firewall rules and role‑based access.

A solid foundation prevents the same operational issues that caused the original stall.

8. Deliver in two‑week sprints with continuous demo

Each sprint follows the same rhythm:

1. Plan, select backlog items that align with the milestone.
2. Build, engineers write code, commit to Git, and the CI pipeline builds a Docker image.
3. Demo, at sprint end, showcase working software to stakeholders; collect feedback immediately.
4. Retrospect, decide what to adjust for the next sprint.

This cadence mirrors Afriq Silicon’s proven agile practice and keeps the project visible to procurement officers and donors.

9. Handover with runbooks and monitoring dashboards

When the final milestone is reached:

• Deliver a runbook that explains start‑up, backup, rollback and incident response procedures.
• Provide access to a monitoring dashboard for real‑time health monitoring.
• Conduct a knowledge‑transfer session with the client’s operations team.
• Support is available during the early operational phase.

10. Checklist for a clean rescue

Use this checklist to verify that nothing falls through the cracks.

Related reading

• Procurement friendly software contract clauses for Kenyan government projects
• Procurement ready rfp template for AI ML projects in African public sector
• Team as a service taa s vs in house hiring what large scale African tech projects actually need

You now have a clear path to bring a stalled government digital project back to life, talk to our team about it.

Photo by Christina Morillo on Pexels.