Deciding what to build and when.
WHAT TO ESTABLISH FIRST
The goal, and how you would know it was achieved.
WHAT TO AVOID
Planning in terms of features without a goal.
WHY
Features are a means; without a goal nobody can judge which matter.
WHAT TO BREAK WORK INTO
Pieces small enough to understand and estimate.
WHY
Small pieces are estimated far more accurately, and finishing them provides feedback.
WHAT TO PRIORITISE BY
Value delivered Risk reduced What blocks other work
WHY RISK
Building the uncertain part early reveals whether the approach works.
WHAT NOT TO PRIORITISE BY
Ease alone Who asked most loudly
WHAT TO SEQUENCE
Anything blocking others, first.
WHAT TO PLAN FOR
The work people forget: testing, review, deployment, documentation, meetings, and fixing what breaks.
WHAT PROPORTION THAT IS
Substantial. Frequently more than the coding itself.
WHAT TO BUILD IN
Slack, because something always arises.
WHAT TO REVISIT
The plan, as you learn.
