liveBook · Manning

Entry criterion

As explained in Build High Value Software Systems

An entry criterion is a condition that work must satisfy before implementation begins.

Entry criteria are conditions work must satisfy before implementation begins. They prevent false starts by ensuring key decisions and validation needs are clear before code is written. section 1.2.3 section 1.2.4

Before implementation begins, confirm:

  • The architectural approach is agreed upon. section 1.2.3
  • The test environment can validate the change. section 1.2.3
  • Acceptance criteria are specific enough for the developer and product manager to make the same decisions independently. section 1.2.3

Make readiness visible

A pull-request template can require the architectural approach to be documented, the test environment validated, and acceptance criteria reviewed with product before a PR is marked ready for review. section 1.2.3

Figure 1.4 Work loop with Lean interventions, addressing specific failure modes from the notification preferences scenario.

Locate entry criteria at the Intent → Code transition, where Value & Pull prevents implementation from starting on unclear assumptions. section 1.2.4

How Build High Value Software Systems covers it

How deep it goes
Specify three readiness conditions and make them visible through a required pull-request checklist.
Examples
Use a pull-request template to document architecture, validate the test environment, and review acceptance criteria with product.
What you can do after
Apply it through a pull-request checklist that keeps work out of implementation until readiness conditions are met.
How it connects
Connect entry criteria to architectural decisions, test environments, acceptance criteria, and pull-request readiness.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.