# Mission: Agile Development

## Why

Ship real work, solo or with one or two others, in increments small enough that progress is visible every few days and a wrong turn costs days rather than months. No scrum master, no ceremony theatre — just the handful of agile practices that actually change what gets delivered when nobody is managing the process for you.

## Success looks like

- Cut any fuzzy feature into thin **vertical slices**, each one finishable in a day and demoable on its own
- Decide what *not* to build — set an appetite (fixed time, variable scope) instead of an estimate
- Run a board that shows the true state of work, with a WIP limit that stops half-finished work piling up
- Know your own **cycle time** and use it to forecast honestly, without story points
- Take what works from Scrum and Kanban and say clearly why the rest doesn't apply at this size
- Run a lightweight review + retro rhythm alone that actually changes the next week's work

## Constraints

- Solo / founder context: no team to coordinate, no Scrum Master, no PO. Every practice must survive a team of one.
- Starting level: has read some theory, practised little. Vocabulary is familiar; the habits are not.
- Wants both Scrum and Kanban covered — flow-first, with Scrum framed as one packaging of the same ideas.
- Lessons must be short enough to finish in one sitting.

## Out of scope

- Enterprise scaling frameworks (SAFe, LeSS, Nexus) and certification prep (PSM/CSM)
- Team-management topics that require a team: capacity planning, velocity per team, cross-team dependency management
- Tooling administration (Jira configuration, board plugins)