E2E Bug PM Review Process (Phase 3)

Overview

After all Phase 2 investigation reports are complete, the PM reviews them to identify patterns, group related bugs, and determine strategic fix approaches.


Step 1: Pattern Recognition

Group Bugs By:

Same Root Cause

Same Component/Domain

Same Integration Boundary

Same Architectural Pattern


Step 2: Fix Strategy Decision

Decision Matrix

Bug Pattern Fix Strategy Rationale
Single isolated bug Isolated Fix No systemic impact, straightforward fix
Multiple bugs, same root cause Batch Fix Fix root cause once, resolves all
Multiple bugs, same component Refactoring Batch Design issue in component
Bugs violate domain rules Domain Model Update Domain understanding gap
Bugs reveal pattern failure Architectural Change Pattern needs redesign (ADR required)

Fix Strategy Types

Isolated Fixes

Refactoring Batch

Domain Model Update

Architectural Change


Step 3: Fix Assignment

Create Epic/Issue for Fix Batch

Epic Template:

Assign to Agent

Agent Selection:

Requirements for Fix Assignment

MANDATORY:


Step 4: Review Fix Execution

Verify Fix Protocol Followed

Check that agent followed:

  1. ✅ Write Failing Test (TDD)
  2. ✅ Verify Domain Model (DDD - check services/domain/models.py)
  3. ✅ Find Existing Patterns (Excellence Flywheel - verification first)
  4. ✅ Implement Minimal Fix (Inchworm - complete 100%)
  5. ✅ Lock with Regression Tests
  6. ✅ Document Decision (ADR if architectural change)
  7. ✅ Verify with E2E Test (original bug scenario)

Completion Criteria


Decision Log

Date: YYYY-MM-DD Bugs Reviewed: #[N], #[N], #[N]

Patterns Identified:

Fix Strategy Decisions:

Epics Created:

Status: [ ] Review complete, [ ] Fixes assigned, [ ] Fixes verified