Scope & MVP
v1 Scope: Compliance Checklist Validation
Goal: Prove that automated compliance checking works for QMS artifact validation.
Core capability: Ingest project artifacts (test strategy, implementation plan, business case, value statement) and validate them against a QMS compliance checklist. Flag missing sections, incomplete data, and deviations from standards.
What's IN v1
- Document upload interface (manual submission for now)
- QMS compliance checklist (basic: ~20-30 items covering Agile/Waterfall standards)
- Artifact validation engine (does the document have required sections? is data complete?)
- Deviation flagging (gaps vs. QMS standards)
- Compliance dashboard (view uploaded artifacts, audit status, flagged issues)
- Human review workflow (auditor reviews findings, validates, submits for approval)
- Basic reporting (compliance summary, issues list, export to PDF/CSV)
- Role-based access (auditor, manager view separation)
What's OUT of v1 (Deferred to v2/v3)
- Cross-document anomaly detection: Comparing inconsistencies across multiple docs (v2)
- Automated artifact source integration: Direct SharePoint/Confluence API pulls (v2)
- AI-powered recommendations: Suggesting fixes for flagged issues (v2+)
- Automated signoff routing: Workflow enforcement and approval tracking (v3)
- Market-specific rule customization: Regional QMS variants (v2+)
- Historical audit trails: Full change tracking and audit history (v2)
- Multi-project batch auditing: Running audits on 100+ projects at once (v2)
- Integration with HRM/SSO: LDAP, OAuth, etc. (v2)
User Journey (v1)
- Auditor logs in → Dashboard shows available projects and audit status
- Uploads artifacts → Selects project, uploads test strategy + implementation plan + business case + value statement
- System validates → Runs against QMS checklist, generates findings report
- Reviews findings → Dashboard shows flagged issues, auditor reads each one, marks as valid/invalid/needs clarification
- Submits for approval → Auditor marks audit complete, routes to compliance manager
- Manager approves → Reviews findings, approves or rejects, signs off
- Audit closed → Dashboard updates, findings locked, export available
QMS Checklist v1 (Draft)
PENDING Full QMS standards definition from Chin
Rough categories (to be expanded):
| Category | v1 Items | Validation Type |
|---|---|---|
| Test Strategy | Scope defined, test levels specified, coverage plan, traceability matrix | Presence check, completeness |
| Implementation Plan | Timeline, milestones, resource allocation, dependency map, risk register | Presence check, consistency with other docs |
| Business Case | Business justification, ROI, assumptions, success criteria, stakeholder sign-off | Presence check, approval chain |
| Value Statement | Project value, user benefits, market fit, alignment with org goals | Presence check, clarity assessment |
| Governance | Approval signatures, document version, date, author, review dates | Presence check, signature validation |
Data to Capture v1
- Project name & identifier
- Organization/market
- Methodology (Agile / Waterfall)
- Document versions (upload date, author)
- QMS compliance score (% checklist passed)
- Flagged issues (issue ID, category, severity, status)
- Audit approver & sign-off date
Manual vs. Built
Can be manual initially (v1):
- Artifact assessment — Human judgment for borderline cases
- Rule customization — Market-specific rules added via config file, not UI
- Approval routing — Send findings via email, collect sign-offs manually (v2 automates this)
Must be built (v1):
- Artifact upload and storage
- Checklist validation engine
- Dashboard UI
- Basic reporting