Search across all documentation pages
Agile frameworks are tools - not goals. Python teams adapt Scrum, Kanban, or SAFe layers so ceremonies improve feedback, WIP stays sane, and Definition of Done includes tests, observability, and safe deploy - not story-point theater.
Quick-reference recipe card - copy-paste ready.
## Definition of Done (Python service)
- [ ] Spec or RFC link for M/L work
- [ ] pytest green; coverage on new paths
- [ ] Ruff + pyright clean on touched packages
- [ ] Structured logs / metrics for new flows
- [ ] Feature flag or rollback noted in PR
- [ ] Deployed to staging; smoke documented
- [ ] Release notes if customer-visibleWhen to reach for this:
## Squad cadence (hybrid Scrum/Kanban)
**Planning (biweekly, 90 min):** Capacity = velocity minus 20% platform
**Daily (15 min):** Blockers only; deep dives offline
**Review (biweekly):** Demo staging + DORA snapshot
**Retro (biweekly):** One experiment action item
**Kanban:** WIP max 3 per engineer; column limits on Review
**SAFe layer (quarterly):** PI planning input = engineering 1-pager only
**Skip:** team-level SAFe metrics rollup if unused# Board automation example - link ticket to deploy state
DONE_CRITERIA = {
"merged": False,
"staging_deploy": False,
"prod_behind_flag": True, # acceptable done for large features
}What this demonstrates:
| Ceremony | Healthy signal | Unhealthy signal |
|---|---|---|
| Planning | Commitment matches capacity | Overflow every sprint |
| Daily | Unblocks in <24h | Status report to manager |
| Retro | Action item closed | Same complaint 3x |
| Review | Stakeholders see staging | Slides only, no software |
## Sprint spillover rule
If migration not staging-tested by mid-sprint, split story - do not carry untested DDL to demo.| Alternative | Use When | Don't Use When |
|---|---|---|
| Pure Kanban | Support/ops heavy | Fixed marketing launches |
| Shape Up | Six-week bets | Continuous SLA microservices |
| Scrumban | Mixed flow | Team needs strict sprint predictability |
| No sprints | Continuous deploy mature | New team needing rhythm |
90 min for two-week sprint with prepared specs; cancel if backlog ungroomed.
Use rolling average; separate platform vs feature throughput optionally.
Often overkill; borrow PI planning calendar only if multi-team deps real.
Re-estimate; split; investigate systemic overcommit in retro.
Reduced: test + rollback path + post-deploy monitor; full DoD follow-up ticket.
Async grooming comments; live planning/review; recorded demos.
Plan 15-20% buffer or explicit interrupt column on Kanban.
Spike stories for data unknowns; done includes eval metric threshold.
Team retro experiment; EM removes organizational blockers.
CFR, review latency, WIP age - one chart beats opinion debates.
Stack versions: This page was written for Python 3.14.0 (stable 3.14, maintenance 3.13), FastAPI 0.115+, Django 5.2, Flask 3.1, Pydantic 2, PyTorch 2.6+, pandas 2.2+, Polars 1.x, ruff 0.9+, and uv 0.6+.
Reviewed by Chris St. John·Last updated Jul 16, 2026