liveBook · Manning

Milestone

As explained in "Looks Good to Me"

A planned intermediate checkpoint at which a developer’s work is reviewed during implementation rather than only at final submission.

A review milestone is a planned check-in during implementation, positioned between full pair programming and a single final code review. An experienced teammate reviews current work, answers questions, and helps align it with the codebase and team standards. section 8.6

Choose intervals that match the developer’s experience, task risk, and need for guidance:

  • Review after an initial implementation or bug fix. section 8.6
  • Review throughout a feature, such as after every commit when substantial guidance is needed. section 8.6
  • Schedule checks at task assignment, halfway through the deadline, and immediately before opening a formal pull request. section 8.6

Supporting a new teammate

Start with clear acceptance criteria and reference samples, review the first implementation, and provide feedback before the pull request. As the developer reaches milestones successfully, reduce the hands-on guidance while retaining useful check-ins. section 8.6 section 8.7

How "Looks Good to Me" covers it

How deep it goes
Defines milestone timing and responsibilities, but stops short of prescribing one universal interval.
Examples
Uses initial implementations, bug fixes, commits, task assignment, halfway points, and pre-pull-request checks.
What it assumes
Assumes a teammate, shared codebase, team standards, and acceptance criteria; supports developers unfamiliar with them.
What you can do after
Apply review milestones to provide timely feedback and gradually reduce guidance as developer confidence grows.
How it connects
Connects review milestones with code review, pair programming, pull requests, acceptance criteria, and codebase standards.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of "Looks Good to Me". The section links point to the parts of the book it draws on.