liveBook · Manning

Review focus

As explained in "Looks Good to Me"

The set of concerns and properties that reviewers are expected to examine in a code change.

Review focus is the agreed outline of what reviewers will concentrate on during a code review. It forms one of four essential team guidelines, alongside workflow, blocking rules, and approver policy. section 3.3.4

Team-wide changes

A pull request changing the Team Working Agreement or migrating to a new API version gives the team a concrete scenario for checking whether its review focus and approval expectations are clear. section 3.3.4

How "Looks Good to Me" covers it

How deep it goes
Defines the need to outline reviewer concerns but does not enumerate those concerns or provide a review checklist.
Examples
Uses Team Working Agreement changes and API-version migrations as team-wide change scenarios.
What it assumes
Assumes a team is shaping a code review process and its approval policy.
What you can do after
Configure a team code-review process by outlining what reviewers will concentrate on.
How it connects
Connects to code review workflow, nonblocking versus blocking issues, and approver policy.
Cover of "Looks Good to Me"
liveBookmanning.com
Read "Looks Good to Me" on liveBook Get the book at manning.com

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.