Overview
The Agile Workflow 🚀
This section is your operational handbook: how raw ideas evolve into released increments week after week.
Flow Overview
- Planning Labs (A → B → C) create the process + knowledge + roadmap substrate.
- Scaffolding ensures the toolchain (repo, CI, test harness) is real, not hypothetical.
- Iterations convert roadmap slices into tested, demoable product increments.
- Feedback (retro + status) informs backlog reshaping—roadmap is adaptive not immutable.
Planning Labs (Weeks 1–6)
Summaries live in the Course Overview index; detailed expectations in Deliverables. Treat each lab as building a different dimension of readiness: social (A), problem/solution clarity (B), strategic execution & quality (C), technical bootstrapping (Scaffolding).
Iteration Operating Rhythm (Weeks 6–17)
Core 10‑step lifecycle (see Phase 2 page) reinforces consistency: Plan → Spike (if needed) → Dev → PR → Review → Test → Merge → Demo → Report → Groom.
Definition of Ready / Done Enforcement
Embed DoR/DoD into workflow—not a side document: - Add a DoR checklist to issue template (hidden HTML comments ok) - Add a DoD checklist section to PR templates - Reject (politely) work that skips criteria → protects team throughput
Backlog Hygiene Signals
| Smell | Action |
|---|---|
| Many “In Progress” cards stale > 3 days | Swarm or slice smaller |
| PR queue > 5 open | Prioritize reviews over starting new work |
| Roadmap goals vague | Refine into outcome statements |
| Issues without acceptance criteria | DoR gate; send back for clarification |
Adaptation vs Thrash
Changing the plan is healthy if grounded in new information (user insight, risk realized). Avoid reactive churn (rewriting roadmap weekly). Use status report “Adjustments” section to justify meaningful shifts.
Artifact Traceability
| Question | Where to Look |
|---|---|
| Why did we choose tech X? | ADR index |
| What’s the current iteration goal? | Iteration Goals issue/doc |
| What changed this week? | Status Report + merged PR list |
| What quality gates matter? | DoD + Test Strategy |
| What risks worry us now? | Risk Register (updated) |
Minimal Metrics (Optional but Helpful)
Lightweight metrics help retros stay empirical: - Lead time (issue start → merge) - PR review turnaround (open → first review) - Spillover count (goals not met) Track for trends, not grading.
Escalation Ladder
Blocked > 24h? Slack thread → issue comment → synchronous huddle → instructor assist (if external dependency). Surface early in Status Report if pattern persists.
Proceed to Phase pages for deeper guidance: - Phase 1: Planning Lab execution details - Phase 2: Iteration lifecycle, role responsibilities in action