Lean waste analysis separates API-delivery work into value-adding activity, enabling activity, and non-value-adding activity. The goal is to increase customer value, minimize enabling work, and eliminate waste. section 2.11
Classify non-value-adding API work using seven waste categories:
- Defects: incorrect API documentation or configurations that cause detection effort and rework. section 2.11
- Overproduction: designing features consumers do not need or use. section 2.11
- Work in process, unnecessary processing, unnecessary motion, unnecessary transport, and waiting. section 2.11
An API review delay
Waiting 11 days for an API review is waste because the work consumes resources without contributing customer value. Eliminating unnecessary handoffs or combining processes can shorten the value stream. section 2.11
