143 lines
4.6 KiB
Markdown
143 lines
4.6 KiB
Markdown
# Methodology Retrospective Task
|
|
|
|
## Purpose
|
|
Conduct systematic retrospective analysis to identify methodology improvements and track effectiveness metrics.
|
|
|
|
## When to Execute
|
|
- After completing any major milestone or phase
|
|
- When encountering significant challenges or inefficiencies
|
|
- At regular intervals during long projects (weekly/bi-weekly)
|
|
- When transitioning between BMAD personas
|
|
|
|
## Instructions
|
|
|
|
### 1. Performance Analysis
|
|
Analyze the recently completed work phase:
|
|
|
|
**Velocity Metrics:**
|
|
- Time from task initiation to completion
|
|
- Number of iterations required to reach acceptable quality
|
|
- Frequency of rework or significant revisions
|
|
|
|
**Quality Metrics:**
|
|
- Clarity and completeness of deliverables
|
|
- Alignment between outputs and requirements
|
|
- Downstream usability (how well outputs served subsequent phases)
|
|
|
|
**Satisfaction Metrics:**
|
|
- User feedback on process effectiveness
|
|
- Ease of execution for the persona
|
|
- Stakeholder satisfaction with outcomes
|
|
|
|
### 2. Pattern Identification
|
|
Look for recurring patterns:
|
|
|
|
**Successful Patterns:**
|
|
- Which techniques, approaches, or workflows worked exceptionally well?
|
|
- What conditions contributed to smooth execution?
|
|
- Which persona interactions were most effective?
|
|
|
|
**Problematic Patterns:**
|
|
- Where did bottlenecks or inefficiencies occur?
|
|
- What caused confusion, rework, or delays?
|
|
- Which handoffs between personas were challenging?
|
|
|
|
### 3. Improvement Opportunities
|
|
Based on analysis, identify specific improvements:
|
|
|
|
**Process Enhancements:**
|
|
- Refinements to persona instructions or workflows
|
|
- Better templates or frameworks
|
|
- Improved handoff procedures between personas
|
|
|
|
**Effectiveness Boosters:**
|
|
- Additional capabilities that would improve outcomes
|
|
- Better integration between different BMAD components
|
|
- Enhanced quality control mechanisms
|
|
|
|
### 4. Implementation Recommendations
|
|
For each identified improvement:
|
|
|
|
**Priority Assessment:**
|
|
- High: Critical improvements that significantly impact effectiveness
|
|
- Medium: Valuable enhancements that provide moderate benefits
|
|
- Low: Minor optimizations for future consideration
|
|
|
|
**Implementation Complexity:**
|
|
- Simple: Can be implemented immediately
|
|
- Moderate: Requires some planning or testing
|
|
- Complex: Needs significant design work or user approval
|
|
|
|
**Expected Impact:**
|
|
- Quantified benefits where possible (time savings, quality improvements)
|
|
- Risk assessment for proposed changes
|
|
|
|
### 5. Methodology Update Proposals
|
|
Create specific, actionable proposals:
|
|
|
|
**Persona Instruction Updates:**
|
|
- Specific text changes to persona files
|
|
- New principles or capabilities to add
|
|
- Outdated instructions to remove or modify
|
|
|
|
**Task and Template Improvements:**
|
|
- Enhanced task instructions or frameworks
|
|
- Better template structures or guidance
|
|
- New tasks needed for identified gaps
|
|
|
|
**Workflow Optimizations:**
|
|
- Improved sequence of persona engagement
|
|
- Better integration points between phases
|
|
- Enhanced feedback loops
|
|
|
|
### 6. User Approval Process
|
|
For major changes:
|
|
|
|
**Present Findings:**
|
|
- Clear summary of analysis and recommendations
|
|
- Expected benefits and potential risks
|
|
- Implementation plan and timeline
|
|
|
|
**Seek Approval:**
|
|
- Explicit user confirmation for significant methodology changes
|
|
- Discussion of concerns or alternative approaches
|
|
- Agreement on implementation priorities
|
|
|
|
### 7. Implementation and Tracking
|
|
Once approved:
|
|
|
|
**Apply Changes:**
|
|
- Update relevant persona files, tasks, and templates
|
|
- Modify workflow documentation
|
|
- Update CLAUDE.md if necessary
|
|
|
|
**Document Changes:**
|
|
- Record all changes in the improvement log
|
|
- Note expected outcomes and success metrics
|
|
- Set up tracking for effectiveness validation
|
|
|
|
**Validate Improvements:**
|
|
- Monitor effectiveness of implemented changes
|
|
- Collect feedback on new approaches
|
|
- Plan follow-up retrospectives to assess impact
|
|
|
|
## Output Format
|
|
|
|
Create a structured retrospective report with:
|
|
|
|
1. **Executive Summary** - Key findings and recommendations
|
|
2. **Performance Metrics** - Quantified analysis of recent phase
|
|
3. **Pattern Analysis** - Successful and problematic patterns identified
|
|
4. **Improvement Proposals** - Specific, prioritized recommendations
|
|
5. **Implementation Plan** - Steps to apply approved changes
|
|
6. **Success Metrics** - How to measure improvement effectiveness
|
|
|
|
## Integration with BMAD Evolution
|
|
|
|
This task directly supports the self-improving nature of the BMAD framework by:
|
|
- Providing systematic methodology improvement
|
|
- Ensuring continuous optimization based on real-world usage
|
|
- Maintaining quality while enabling rapid evolution
|
|
- Creating a feedback loop for all BMAD components
|
|
|
|
Execute this task regularly to ensure the BMAD methodology continues to evolve and improve with each project experience. |