ForemanPlanning
Every request becomes a plan first
A plain request is enough. Foreman classifies it, writes a brief with what done means and the command that proves it, and only then lets an edit happen.
What a brief holds
- Type and size. FIX, FEATURE, CLEAN, PERFORMANCE, SECURITY or RESEARCH, and S, M or L.
- Acceptance criteria, each with the command that proves it.
- Steps, scope and risks. M and L work lists its approaches first and says why it chose one.
- An approval when the work is large, unless you put Foreman in full auto.
FIX: login times out after 30s on slow networks FEATURE: export report as CSV @src/reports CONTEXT: Django app; don't touch migrations DONE-WHEN: all tests pass and the CSV opens in Excel
One task at a time
One task is active. New ideas land in the inbox instead of being chased halfway, and the queue orders itself: baseline, cleanups, performance, security, fixes, then features, dependencies first. NOW: switches on purpose.
Show the numbers
| value | |
|---|---|
| S small | 387 |
| M medium | 300 |
| L large | 47 |
Show the numbers
| value | |
|---|---|
| FEATURE | 335 |
| FIX | 239 |
| SECURITY | 68 |
| CLEAN | 46 |
| RESEARCH | 25 |
| PERFORMANCE | 21 |