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
