Tlale Digital
Section 5.0 · Delivery Methodology
5.0

Delivery Methodology

A phased, documented approach. Each phase ends with a deliverable your project manager signs off before work continues.

  1. 5.1 · Phase 1

    Inception

    1 week
    • — Inception report
    • — Project plan & risk register
    • — Stakeholder map
    Sign-off
    Signed inception report
  2. 5.2 · Phase 2

    Discovery

    1–3 weeks
    • — Requirements specification
    • — Current-state assessment
    • — Data & POPIA impact notes
    Sign-off
    Approved requirements
  3. 5.3 · Phase 3

    Design

    2–4 weeks
    • — Information architecture
    • — Interactive prototype
    • — Accessibility review
    Sign-off
    Approved design
  4. 5.4 · Phase 4

    Build

    4–12 weeks
    • — Fortnightly working releases
    • — Progress reports
    • — Test evidence
    Sign-off
    Sprint acceptance
  5. 5.5 · Phase 5

    UAT

    1–2 weeks
    • — UAT plan & scripts
    • — Defect log & fixes
    • — Go-live checklist
    Sign-off
    UAT sign-off
  6. 5.6 · Phase 6

    Handover & Support

    Ongoing
    • — Admin training
    • — User & technical manuals
    • — Support & maintenance plan
    Sign-off
    Close-out report

Durations are typical ranges and are confirmed in the inception report for each project.

5.7Governance & Reporting

Weekly

Written progress report: work done, next steps, risks and issues.

Fortnightly

Working software demonstration and sprint acceptance.

Monthly

Steering meeting with budget, timeline and risk review.

5.8Proposed Service Levels

Proposed for post-launch support; final levels are agreed in each service level agreement.

PriorityResponseResolution target
Priority 1 — System unavailableWithin 2 business hoursRestore within 1 business day
Priority 2 — Major function impairedWithin 4 business hoursResolve within 3 business days
Priority 3 — Minor issue / requestWithin 1 business dayScheduled in next release

5.9Risk Management

Scope change

Formal change requests with impact on cost and time approved before work.

Data protection

POPIA impact notes at discovery; least-privilege access in production.

Continuity

Source code, documentation and credentials handed over to the client.

Quality

Peer review, automated tests and UAT evidence before every release.

Have a tender or RFQ?Submit RFQ