Skip to content

tracker-functional-audit.md

Latest commit

 

History

History
145 lines (123 loc) · 9.68 KB

tracker-functional-audit.md

File metadata and controls

145 lines (123 loc) · 9.68 KB
Raw

Tracker Functional Audit

Audit Role: Product Owner (BMAD)
Audit Date: 2026-06-07
Method: BMAD · Evolith Tracker Documentation Audit

1. Functional Audit Summary

Area Status Finding Count
Product Vision DEFINED 2 gaps
Problem Statement DEFINED 0 gaps
Value Proposition DEFINED 0 gaps
Target Users / Actors DEFINED 0 gaps
Business Objectives DEFINED 1 gap
Functional Scope PARTIALLY_DEFINED 3 gaps
Business Rules PARTIALLY_DEFINED 2 gaps
Use Cases DEFINED 0 gaps
Acceptance Criteria PARTIALLY_DEFINED high-level only
Prioritization DEFINED MoSCoW applied
Dependencies DEFINED 1 gap
Risks PARTIALLY_DEFINED informal only
Metrics DEFINED 8 metrics
Roadmap PARTIALLY_DEFINED missing dates
Separation Tracker/Core DEFINED 0 gaps
External Integrations PARTIALLY_DEFINED 3 gaps

Overall PO Coverage: PARTIALLY_DEFINED

2. Capacity Status by Feature

Capability Source Status Notes
Discovery Gate (Initiative + Canvas) PRD EPIC-000, Product Brief UC-001 DEFINED BR-001 clear; Canvas format defined
Discovery Gate Business Approval PRD EPIC-000 DEFINED Approval/rejection flow specified
OKR Alignment PRD EPIC-000 (Could Have) DEFINED Priority justified
Design — Contract Generation PRD EPIC-001, Functional Scope DEFINED OpenAPI/AsyncAPI mentioned
Design — GraphQL Contracts Functional Scope Design only AMBIGUOUS PRD says "OpenAPI/AsyncAPI"; Functional Scope adds GraphQL; no ADR decision
Design — ADR Management PRD EPIC-001 DEFINED Must Have
Design — Upstream Compliance Check PRD EPIC-001 DEFINED Must Have
Design — Architecture Gate PRD EPIC-001 DEFINED Must Have
Design — Technical Blueprint PRD EPIC-001 DEFINED Must Have
Construction — Spec Traceability PRD EPIC-002 DEFINED Must Have
Construction — Architecture Drift Detection PRD EPIC-002, Product Vision DEFINED Core differentiator
Construction — Architecture Drift Index PRD EPIC-002 DEFINED Must Have
QA — .harness Integration PRD EPIC-003 DEFINED Must Have; ACL spec missing
QA — Contract Test Execution PRD EPIC-003 DEFINED Must Have
QA — CFR Tracking (< 2%) PRD EPIC-003 DEFINED Criterion measurable
QA — Root Cleanliness PRD EPIC-003 DEFINED Must Have
Release — Deployment Calendar PRD EPIC-004 DEFINED Must Have
Release — Regression Score Integration PRD EPIC-004 DEFINED Must Have
Release — Re-Do Flow PRD EPIC-004, Product Vision DEFINED Core differentiator
Release — DORA Metrics PRD EPIC-004, EPIC-006 DEFINED 4 metrics specified
Release — SPACE Metrics PRD EPIC-004 (Should Have) PARTIALLY_DEFINED Mentioned but not detailed
BMAD Agent Assignment PRD EPIC-005 DEFINED Must Have
BMAD Agent Audit Log PRD EPIC-005 DEFINED Must Have
Deliverable Validation Pipeline PRD EPIC-005 DEFINED Must Have
MCP Server PRD EPIC-005 DEFINED Must Have; 6 tool categories
CLI Interface PRD EPIC-005, EPIC-000–004 DEFINED Must Have; verb-noun structure
Dual-Track Configuration PRD EPIC-005, Product Vision DEFINED Must Have
Analytics — DORA Engine PRD EPIC-006 DEFINED Must Have
Analytics — Adherence Index PRD EPIC-006 DEFINED Must Have
Analytics — Initiative Dashboard PRD EPIC-006 DEFINED Must Have
Multi-Tenancy PRD §8, Product Vision DEFINED TenantID isolation confirmed
UMS Integration (AuthN/AuthZ) PRD §10, Product Vision DEFINED Out of scope for Tracker's own user management
External Tool Export (Jira/Trello) PRD EPIC-000 (Should Have) DEFINED Priority clear
Billing / Subscription PRD §11 (Out of Scope) DEFINED Correctly scoped out
Custom Methodology Builder PRD §11 (Out of Scope) DEFINED Correctly scoped out
IDE Plugin PRD §11 (Out of Scope) DEFINED Correctly scoped out

3. Business Rules Analysis

Rule ID Rule Verifiable? Source Status
BR-001 No initiative advances to Design without cleared Discovery Canvas YES — gate is a system lock Product Brief, PRD DEFINED
BR-002 No construction begins without approved Technical Blueprint YES — gate is a system lock Product Brief, PRD DEFINED
BR-003 No deployment without passing QA Quality Gate YES — CFR < 2% is measurable Product Brief, PRD DEFINED
BR-004 Architecture Drift triggers automatic alert YES — Drift Index metric Product Brief, PRD DEFINED
BR-005 All governance rules inherited from Evolith Core (upstream immutability) YES — DECISIONS.md tracks divergences Product Brief, PRD DEFINED
BR-006 Multi-tenant isolation absolute; no cross-TenantID data YES — RLS + TenantID Product Brief, PRD DEFINED
BR-007 BMAD Agent deliverables equivalent to human for gate evaluation YES — validation pipeline Product Brief, PRD DEFINED
BR-008 CLI and MCP = Web UI feature parity YES — parity audit metric Product Brief, PRD DEFINED
BR-009 All BMAD agent interactions logged and auditable YES — audit log Product Brief, PRD DEFINED
— Multi-tenancy application-layer isolation primary, DB secondary DEFINED global-rules.md R-15 NOT IN PRODUCT BRIEF — gap
— No Release phase authorization before Design gate passes IMPLICIT in gate sequence PRD §7 orchestration PARTIALLY_DEFINED — needs explicit BR

4. Use Case Analysis

UC Name Inputs Output States Source Status
UC-001 Validate Business Initiative Raw idea, ROI data, KPIs Discovery Canvas; Go/No-Go verdict Draft → Submitted → Approved / Rejected Product Brief DEFINED
UC-002 Generate Technical Contract Approved Initiative OpenAPI/AsyncAPI specs, ADRs, Technical Blueprint Draft → Submitted → Compliant / Non-Compliant → Approved Product Brief DEFINED
UC-003 Track Construction Against Spec Technical Blueprint, code commits Architecture Drift alerts, Drift Index In-Progress → Drift Alert / Clean Product Brief DEFINED
UC-004 Execute Automated QA Construction completion, .harness config Test results, CFR rate, QA Gate verdict Pending → Running → Passed / Failed Product Brief DEFINED
UC-005 Plan and Execute Release QA Gate pass, Deployment calendar Release notes, Deployment record, Re-Do Flow Planned → Authorized → Deployed / Rolled Back Product Brief DEFINED
UC-006 Operate in AI-Native Mode Tenant BMAD config Automated SDLC execution without human intervention (except approval gates) Configured → Active → Monitoring Product Brief DEFINED
UC-007 Use Tracker via CLI CLI command + options Machine-readable output; state change Interactive → Complete Product Brief, PRD §5.2 DEFINED
UC-008 Connect BMAD Agent via MCP MCP tool call Structured response (assignment / spec / gate status) Connected → Authorized → Result returned Product Brief, PRD §5.3 DEFINED

5. PO Criteria Gaps (Require Human Decision)

GAP-F-001 — GraphQL as Contract Format

  • Finding: functional-scope.md (Design) mentions GraphQL schemas as a contract format. The PRD specifies "OpenAPI for synchronous APIs, AsyncAPI for events" only.
  • Impact: Developers and agents may generate GraphQL schemas that are not tracked or validated by the QA gate.
  • Severity: HIGH
  • Recommendation: PO to confirm: Is GraphQL a first-class contract format in Phase 1? If yes, update PRD EPIC-001 and add GraphQL compliance to the QA gate. If no, remove from functional-scope.md.
  • Requires PO Decision: YES
  • Can auto-correct: NO

GAP-F-002 — SPACE Metrics Not Detailed

  • Finding: SPACE metrics referenced as "Should Have" in EPIC-004 but no specific SPACE indicators (Satisfaction, Performance, Activity, Communication, Efficiency) are defined.
  • Impact: Cannot build scorecard without metric definition.
  • Severity: MEDIUM
  • Recommendation: PO to define which SPACE sub-metrics to implement in Phase 1.
  • Requires PO Decision: YES
  • Can auto-correct: NO

GAP-F-003 — Formal Risk Register Missing

  • Finding: Risks are mentioned informally in PRD (UMS Dependency, Phase 1 Scope) but no formal Risk Register document exists.
  • Impact: Implementation planning cannot formally assess risk probability/impact.
  • Severity: MEDIUM
  • Recommendation: Create a tracker-risk-register.md with probability, impact, and mitigation per risk.
  • Can auto-correct: NO (requires PO input)
  • Status: ✅ RESOLVED (2026-06-07) — Created reference/governance/tracker-risk-register.md: 15 risks (R-01..R-15) with probability/impact/severity/mitigation/owner. No Critical; 6 High (external deps + pending PO decisions).

GAP-F-005 — Roadmap Has No Dates

  • Finding: The Implementation Roadmap in TAD lists 8 phases with "S" (Small) and "M" (Medium) durations — these are relative and undefined.
  • Impact: Cannot plan releases or commitments.
  • Severity: MEDIUM
  • Recommendation: PO to define Phase 0 start date and duration expectations to convert relative to absolute dates.
  • Can auto-correct: NO (requires PO decision)

Generated by: PO Audit Role (BMAD) · 2026-06-07