# Notes

## User preferences

- Solo / founder. Every practice taught must work with a team of one — if it needs a Scrum Master, a PO, or a second pair of eyes, either adapt it explicitly or say it doesn't apply.
- Has read some agile theory, practised little. The gap is **habit**, not vocabulary. Don't spend lessons defining terms he has already read; spend them on doing.
- Wants Scrum *and* Kanban. Teaching order: flow concepts first (they survive at solo scale), Scrum framed later as one particular packaging of the same ideas.
- Also learning Git in the sibling workspace. Same taste applies: short lessons, one tangible win, model over recipe.

## Teaching notes

- Agile's difficulty is the inverse of Git's: the vocabulary is *over*-familiar and hollowed out by corporate misuse. Every term used in a lesson must be pinned to a primary-source definition in `reference/agile-glossary.html`, not to the industry folk meaning.
- Bias every lesson toward something he can do to his own real work this week. Abstract examples are the failure mode for this topic.
- Resist teaching ceremonies. At solo scale, the ceremonies are the least transferable part; slicing, WIP limits, and cycle time are the parts that pay.

## Session log

- 2026-07-24 — Workspace created. Mission set (solo/small-team delivery). Lesson 0001 (the vertical slice) delivered, with glossary + splitting-patterns reference cards.