Workstreams & Dependencies

v1 Workstreams

These are the numbered work packages required to ship v1. Dependencies and build sequencing shown below.

Workstream Overview

WSTitleDescriptionEst. EffortOwnerStatus
WS-1Project Setup & InfrastructureGit repo, CI/CD, database schema, deployment pipeline, dev environment1-2 weeksTBDNOT STARTED
WS-2Authentication & User ManagementLogin flow, role-based access (auditor/manager), user database schema1 weekTBDNOT STARTED
WS-3QMS Checklist Definition & StorageDefine v1 QMS compliance checklist, store in database, create management API2-3 weeksChin (input), Build Team (implement)BLOCKED (needs Chin input)
WS-4Artifact Upload & StorageFile upload API, document storage (S3 or local), metadata management2 weeksTBDNOT STARTED
WS-5Validation EngineDocument parsing, checklist validation logic, finding generation3-4 weeksTBDNOT STARTED
WS-6Dashboard UI (Auditor)Project list, audit detail view, findings review interface3 weeksTBDNOT STARTED
WS-7Approval Workflow UI (Manager)Approval dashboard, audit summary, sign-off forms2 weeksTBDNOT STARTED
WS-8Reporting & ExportCompliance report generation, PDF/CSV export, audit trail logging2 weeksTBDNOT STARTED
WS-9Testing & QAUnit tests, integration tests, UAT with compliance team2-3 weeksTBDNOT STARTED
WS-10Deployment & LaunchProduction environment setup, data migration, go-live support1 weekTBDNOT STARTED

Dependency Map


FOUNDATIONS (No dependencies, can start immediately)
├─ WS-1: Project Setup & Infrastructure
├─ WS-2: Authentication & User Management
├─ WS-3: QMS Checklist Definition (blocked on Chin input)
└─ WS-4: Artifact Upload & Storage

DEPENDENT ON FOUNDATIONS
├─ WS-5: Validation Engine
│  ├─ Depends on: WS-3 (checklist), WS-4 (artifacts)
│  └─ Enables: WS-6, WS-7, WS-8
├─ WS-6: Dashboard UI (Auditor)
│  ├─ Depends on: WS-1 (infra), WS-2 (auth), WS-5 (validation engine)
│  └─ Can run parallel with WS-7
└─ WS-7: Approval Workflow UI (Manager)
   ├─ Depends on: WS-1 (infra), WS-2 (auth), WS-5 (validation engine)
   └─ Can run parallel with WS-6

DEPENDENT ON UI & ENGINE
├─ WS-8: Reporting & Export
│  ├─ Depends on: WS-5 (engine), WS-6, WS-7 (UIs)
│  └─ Enables: WS-9 (UAT)
├─ WS-9: Testing & QA
│  ├─ Depends on: WS-6, WS-7, WS-8
│  └─ Enables: WS-10
└─ WS-10: Deployment & Launch
   └─ Depends on: WS-9 (passed QA)

Build Sequencing (Foundation vs. Dependent)

PhaseDurationWorkstreamsParallelizableGate
Phase 1: Foundation2-3 weeksWS-1, WS-2, WS-3*, WS-4WS-1, WS-2, WS-4 can run parallel; WS-3 blocked on Chin inputAll foundational systems stable (infra, auth, checklist, storage)
Phase 2: Core Engine & UI4-5 weeksWS-5, WS-6, WS-7WS-6 and WS-7 can run parallel; both depend on WS-5 progressValidation engine working, both UIs rendering findings correctly
Phase 3: Reporting & QA3-4 weeksWS-8, WS-9WS-8 and WS-9 sequential (reports tested in QA)All feature tests passing, UAT complete
Phase 4: Launch1 weekWS-10N/AGo-live readiness

Critical Path

Longest dependency chain (all nodes on critical path must complete for go-live):


WS-1 (Setup)
  ↓
WS-3 (Checklist) [BLOCKED ON CHIN INPUT]
  ↓
WS-5 (Validation Engine)
  ↓
WS-6 + WS-7 (UI, parallel)
  ↓
WS-8 (Reporting)
  ↓
WS-9 (QA)
  ↓
WS-10 (Launch)

CRITICAL BLOCKER: Chin must provide QMS checklist definition to unblock WS-3.
ESTIMATED DURATION: 10-13 weeks (if all tasks execute as estimated, WS-3 unblocked on week 1).

Risk Mitigation - Build Sequencing

Note: Effort estimates are rough and assume TBD build team capability. Once team is defined, refine estimates and adjust timeline.