Root-cause sprint

Who this is for

Product engineering leads, SRE managers, and CTOs of small-to-mid software teams in South Africa and neighbouring markets. You have a defect with business impact, internal effort has stalled, and you need an external investigator who will work alongside your developers rather than audit from a checklist.

What you receive

• Daily written update (maximum one page) summarising hypotheses tested and evidence gathered
• Final root-cause report with failure diagram, triggering conditions, and recommended fix order
• Optional 60-minute handover session with your team to walk through reproduction steps
• All investigation artefacts stored in your repository or ticket system—you retain ownership

Excluded: large-scale refactors, ongoing on-call coverage, and security penetration testing. We can recommend specialists if those needs appear during the sprint.

How the week runs

1. Day 0 — Briefing (remote, 90 minutes)

   You describe symptoms, impact, and what has already been ruled out. We agree success criteria and access paths.

2. Days 1–2 — Observation and instrumentation

   We read existing logs, add narrowly scoped diagnostics where needed, and attempt reproduction in staging or a shadow environment.

3. Days 3–4 — Narrowing and confirmation

   Hypotheses are eliminated with experiments. We pair with your engineer when touching unfamiliar subsystems.

4. Day 5 — Report and handover

   Written root-cause document delivered; handover call scheduled within two business days if requested.