liveBook · Manning

Value-enabling work

As explained in Automating API Delivery

Value-enabling work does not directly create the finished customer-valued output but is required under current conditions for value-adding work to occur.

Value-enabling (VE) work does not transform inputs into the finished output customers value, but current conditions require it before value-adding (VA) work can proceed. It differs from waste: VE enables delivery, while waste consumes resources without contributing customer value. section 2.11

Classify activities in the value stream and improve them by:

  • Recognizing acceptance and security tests as VE because they expose problems that must be fixed before delivery. section 2.11
  • Treating API reviews and requirements tickets as enabling activities rather than customer-valued output. section 2.11
  • Minimizing VE work where possible, increasing VA work, and eliminating non-value-adding activity such as waiting and unnecessary handoffs. section 2.11

How Automating API Delivery covers it

How deep it goes
Defines VE work, contrasts it with VA work and waste, and explains its improvement direction through API examples.
Examples
Uses acceptance and security tests, API reviews, and requirements tickets as VE examples, while waiting illustrates waste.
What you can do after
Evaluate activities by whether they enable value-adding work, then minimize VE activity and eliminate waste.
How it connects
Connects value-enabling work to value-adding work, waste, acceptance testing, security testing, API reviews, and handoffs.
Cover of Automating API Delivery
liveBookmanning.com
Read Automating API Delivery on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.