|
| 1 | +# Sprint/Cycle Management - Implementation Summary |
| 2 | + |
| 3 | +## What Was Created |
| 4 | + |
| 5 | +### 1. Design Document |
| 6 | +**File**: `SPRINT_CYCLE_DESIGN.md` |
| 7 | + |
| 8 | +Comprehensive design for sprint/cycle management including: |
| 9 | +- Directory structure |
| 10 | +- New commands (`/speckit.sprint`, `/speckit.retrospective`, `/speckit.roadmap`, `/speckit.archive`) |
| 11 | +- Integration with existing workflows |
| 12 | +- Implementation strategy |
| 13 | +- Benefits and backward compatibility |
| 14 | + |
| 15 | +### 2. Templates |
| 16 | + |
| 17 | +#### Sprint Template |
| 18 | +**File**: `templates/sprint-template.md` |
| 19 | + |
| 20 | +Complete sprint planning template with: |
| 21 | +- Sprint goals and success criteria |
| 22 | +- Feature backlog and priorities |
| 23 | +- Dependencies and risks |
| 24 | +- Daily progress tracking |
| 25 | +- Decision documentation |
| 26 | +- Pivot tracking |
| 27 | +- Sprint metrics |
| 28 | + |
| 29 | +#### Sprint Summary Template |
| 30 | +**File**: `templates/sprint-summary-template.md` |
| 31 | + |
| 32 | +Archival summary template with: |
| 33 | +- Executive summary |
| 34 | +- Goal achievement analysis |
| 35 | +- Completed features list |
| 36 | +- Key decisions with full context |
| 37 | +- Pivots and course corrections |
| 38 | +- Sprint metrics |
| 39 | +- Lessons learned |
| 40 | +- Technical artifacts |
| 41 | +- Impact and value delivered |
| 42 | +- Next sprint preview |
| 43 | + |
| 44 | +#### Retrospective Template |
| 45 | +**File**: `templates/retrospective-template.md` |
| 46 | + |
| 47 | +Structured retrospective template with: |
| 48 | +- What went well / what could improve |
| 49 | +- Decision clarifications (similar to `/speckit.clarify`) |
| 50 | +- Pivot analysis |
| 51 | +- Process and technical practice evaluation |
| 52 | +- Action items with owners |
| 53 | +- Experiments to try |
| 54 | +- Team health and morale |
| 55 | +- Appreciation and recognition |
| 56 | + |
| 57 | +### 3. Commands |
| 58 | + |
| 59 | +#### Retrospective Command |
| 60 | +**File**: `templates/commands/retrospective.md` |
| 61 | + |
| 62 | +Command implementation for conducting retrospectives: |
| 63 | +- Structured question categories |
| 64 | +- Sequential questioning (like `/speckit.clarify`) |
| 65 | +- Decision clarification focus |
| 66 | +- Pivot analysis |
| 67 | +- Action item generation |
| 68 | +- Integration with sprint archives |
| 69 | + |
| 70 | +### 4. Example Integration |
| 71 | + |
| 72 | +#### BA Project Example |
| 73 | +**File**: `SPRINT_BA_EXAMPLE.md` |
| 74 | + |
| 75 | +Real-world example showing: |
| 76 | +- How 33 BA features would be organized into 4 sprints |
| 77 | +- Example sprint summaries |
| 78 | +- Decision clarifications |
| 79 | +- Pivot documentation |
| 80 | +- Benefits for the BA project |
| 81 | +- Retroactive sprint creation process |
| 82 | + |
| 83 | +## Key Features |
| 84 | + |
| 85 | +### 1. Non-Invasive |
| 86 | +- Existing feature workflows unchanged |
| 87 | +- Sprint management is optional |
| 88 | +- Backward compatible |
| 89 | + |
| 90 | +### 2. Archival-First |
| 91 | +- Completed sprints archived with summaries |
| 92 | +- Decisions preserved with context |
| 93 | +- Knowledge not lost |
| 94 | + |
| 95 | +### 3. Decision-Focused |
| 96 | +- Captures WHY decisions were made |
| 97 | +- Documents pivots and course corrections |
| 98 | +- Clarifies unclear choices (retrospective) |
| 99 | + |
| 100 | +### 4. Retrospective-Driven |
| 101 | +- Similar to `/speckit.clarify` but for past decisions |
| 102 | +- Structured questioning process |
| 103 | +- Generates actionable improvements |
| 104 | + |
| 105 | +### 5. Project-Level Visibility |
| 106 | +- Roadmap across sprints |
| 107 | +- Cross-feature dependencies |
| 108 | +- Progress tracking |
| 109 | + |
| 110 | +## How It Addresses Your Requirements |
| 111 | + |
| 112 | +### ✅ Archive a Cycle |
| 113 | +- Sprint archives in `sprints/archive/sprint-NNN/` |
| 114 | +- High-level summaries in `summary.md` |
| 115 | +- All feature specs preserved in `specs/` |
| 116 | + |
| 117 | +### ✅ Highlight Decisions Made |
| 118 | +- `decisions.md` in each sprint archive |
| 119 | +- Full context: options considered, rationale, impact |
| 120 | +- Links to affected features |
| 121 | + |
| 122 | +### ✅ Document Pivots |
| 123 | +- Pivot section in sprint summary |
| 124 | +- Original plan → actual outcome |
| 125 | +- Reason for pivot |
| 126 | +- Lessons learned |
| 127 | + |
| 128 | +### ✅ Retrospective for Clarification |
| 129 | +- `/speckit.retrospective` command |
| 130 | +- Similar to `/speckit.clarify` but for past decisions |
| 131 | +- Structured questions about unclear choices |
| 132 | +- Updates decisions.md with clarifications |
| 133 | + |
| 134 | +## Next Steps |
| 135 | + |
| 136 | +### Phase 1: Core Implementation |
| 137 | +1. Add templates to spec-kit repository |
| 138 | +2. Implement `/speckit.sprint` command |
| 139 | +3. Implement `/speckit.archive` command |
| 140 | +4. Test with single sprint workflow |
| 141 | + |
| 142 | +### Phase 2: Retrospectives |
| 143 | +1. Implement `/speckit.retrospective` command |
| 144 | +2. Test with BA project (retroactive) |
| 145 | +3. Refine questioning process |
| 146 | + |
| 147 | +### Phase 3: Roadmap |
| 148 | +1. Implement `/speckit.roadmap` command |
| 149 | +2. Add cross-sprint visualization |
| 150 | +3. Track dependencies |
| 151 | + |
| 152 | +### Phase 4: Integration |
| 153 | +1. Update existing commands to be sprint-aware |
| 154 | +2. Add sprint linking to `/speckit.specify` |
| 155 | +3. Update documentation |
| 156 | + |
| 157 | +## Files Created |
| 158 | + |
| 159 | +``` |
| 160 | +spec-kit/ |
| 161 | +├── SPRINT_CYCLE_DESIGN.md # Complete design document |
| 162 | +├── SPRINT_BA_EXAMPLE.md # BA project integration example |
| 163 | +├── SPRINT_SUMMARY.md # This file |
| 164 | +└── templates/ |
| 165 | + ├── sprint-template.md # Sprint planning template |
| 166 | + ├── sprint-summary-template.md # Sprint archival template |
| 167 | + ├── retrospective-template.md # Retrospective template |
| 168 | + └── commands/ |
| 169 | + └── retrospective.md # Retrospective command |
| 170 | +``` |
| 171 | + |
| 172 | +## Benefits |
| 173 | + |
| 174 | +1. **Knowledge Preservation**: Decisions and context archived |
| 175 | +2. **Onboarding**: New team members read sprint summaries |
| 176 | +3. **Stakeholder Communication**: Clear progress reports |
| 177 | +4. **Decision Tracking**: Understand why choices were made |
| 178 | +5. **Continuous Improvement**: Retrospectives drive improvements |
| 179 | +6. **Pattern Recognition**: Identify recurring issues |
| 180 | +7. **Project Visibility**: See progress across features |
| 181 | + |
| 182 | +## Comparison: Before vs After |
| 183 | + |
| 184 | +### Before (Current Spec Kit) |
| 185 | +- ✅ Excellent feature-level workflows |
| 186 | +- ❌ No cross-feature visibility |
| 187 | +- ❌ No sprint/cycle concept |
| 188 | +- ❌ No formal retrospectives |
| 189 | +- ❌ Decisions scattered across specs |
| 190 | +- ❌ No project-level roadmap |
| 191 | + |
| 192 | +### After (With Sprint Management) |
| 193 | +- ✅ Excellent feature-level workflows (unchanged) |
| 194 | +- ✅ Cross-feature visibility via sprints |
| 195 | +- ✅ Sprint/cycle management |
| 196 | +- ✅ Structured retrospectives |
| 197 | +- ✅ Decisions consolidated in sprint archives |
| 198 | +- ✅ Project-level roadmap |
| 199 | + |
| 200 | +## Example Workflow |
| 201 | + |
| 202 | +```bash |
| 203 | +# Start a sprint |
| 204 | +/speckit.sprint start "Sprint 1: Authentication & Authorization" --duration 2w |
| 205 | + |
| 206 | +# Add features to sprint |
| 207 | +/speckit.sprint add 001-auth-foundation 002-role-management |
| 208 | + |
| 209 | +# Work on features (existing workflow) |
| 210 | +/speckit.specify Build authentication system |
| 211 | +/speckit.plan Use AWS Cognito |
| 212 | +/speckit.tasks |
| 213 | +/speckit.implement |
| 214 | + |
| 215 | +# Complete sprint |
| 216 | +/speckit.archive |
| 217 | + |
| 218 | +# Conduct retrospective |
| 219 | +/speckit.retrospective |
| 220 | + |
| 221 | +# Update roadmap |
| 222 | +/speckit.roadmap |
| 223 | +``` |
| 224 | + |
| 225 | +## Conclusion |
| 226 | + |
| 227 | +This design adds sprint/cycle management to Spec Kit while: |
| 228 | +- Preserving all existing feature-level workflows |
| 229 | +- Adding project-level visibility |
| 230 | +- Enabling knowledge archival |
| 231 | +- Supporting retrospectives with decision clarification |
| 232 | +- Maintaining backward compatibility |
| 233 | + |
| 234 | +The BA project example demonstrates the value - 33 features with rich decision history that would benefit from sprint-level organization and retrospective analysis. |
| 235 | + |
| 236 | +--- |
| 237 | + |
| 238 | +## Generic Example Added |
| 239 | + |
| 240 | +### File: `SPRINT_GENERIC_EXAMPLE.md` (17KB, 471 lines) |
| 241 | + |
| 242 | +A completely generic, anonymized example based on the BA project patterns that can be used as a template for any project type. |
| 243 | + |
| 244 | +**Contents**: |
| 245 | +- Generic enterprise SaaS application profile |
| 246 | +- 4 sprint pattern (Foundation → Core → Integration → Polish) |
| 247 | +- 35 generic features organized across sprints |
| 248 | +- Example sprint archive (Sprint 002: Core Features) |
| 249 | +- Generic decision clarification examples |
| 250 | +- Generic retrospective template usage |
| 251 | +- Benefits demonstration with before/after comparisons |
| 252 | + |
| 253 | +**Key Patterns Extracted**: |
| 254 | + |
| 255 | +1. **Sprint 001: Foundation** (3-5 features) |
| 256 | + - Project setup, auth, database, API foundation |
| 257 | + - Technology stack decisions |
| 258 | + - Common pivots: auth provider, database choice |
| 259 | + |
| 260 | +2. **Sprint 002: Core Features** (5-8 features) |
| 261 | + - User-facing functionality |
| 262 | + - UI framework, state management, storage decisions |
| 263 | + - Common pivots: search implementation, notification strategy |
| 264 | + |
| 265 | +3. **Sprint 003: Integration & Polish** (8-12 features) |
| 266 | + - Component integration, performance, accessibility |
| 267 | + - Real-time vs polling, caching, monitoring decisions |
| 268 | + - Common pivots: real-time → polling, early caching |
| 269 | + |
| 270 | +4. **Sprint 004: Production Readiness** (5-10 features) |
| 271 | + - Deployment, backup, DR, testing, security |
| 272 | + - Deployment strategy, DR targets decisions |
| 273 | + - Common pivots: simplified deployment, reduced DR scope |
| 274 | + |
| 275 | +**Example Decision Clarifications**: |
| 276 | +- Technology choice (Framework X vs Y) |
| 277 | +- Architecture pivot (Database → Elasticsearch) |
| 278 | +- Scope reduction (Rich UI → Simple MVP) |
| 279 | + |
| 280 | +**Reusable for Any Project**: |
| 281 | +- SaaS applications |
| 282 | +- Mobile apps |
| 283 | +- Data pipelines |
| 284 | +- Infrastructure projects |
| 285 | +- Internal tools |
| 286 | +- Customer-facing products |
| 287 | + |
0 commit comments