liveBook · Manning

Value and pull principle

As explained in Build High Value Software Systems

The value and pull principle is a Lean principle that starts work only when its value and readiness are sufficiently established.

The value and pull principle prevents false starts by keeping work out of implementation until its purpose and readiness are clear. It turns readiness into visible entry criteria rather than relying on assumptions or memory. section 1.2.4 section 1.2.3

Before implementation begins, confirm that:

  • 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 reach the same decisions independently. section 1.2.3

Make readiness visible in a pull request

A PR template can require the architectural approach to be documented, the test environment validated, and acceptance criteria reviewed with product before the 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.

Shows where value and pull intervenes in the work loop: between intent and code. section 1.2.4

How Build High Value Software Systems covers it

How deep it goes
Operationalizes the principle through three readiness checks and a PR-template checklist.
Examples
Uses a notification-preferences change and a PR checklist covering architecture, test validation, and acceptance criteria.
What you can do after
Configure implementation intake with a PR checklist that keeps work from becoming ready for review until readiness checks are complete.
How it connects
Connects Lean to the SDLC work loop, implementation entry criteria, pull requests, and acceptance criteria.

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.