liveBook · Manning

Value-adding work

As explained in Automating API Delivery

Value-adding work, or a value-added activity, is process work that directly contributes to an outcome valued by the customer.

Value-adding work, or a value-added activity, transforms inputs into outputs that customers consider useful and important. External customers demonstrate value through willingness to pay. section 2.11

Classify production activities by their direct contribution to customer value:

  • Value-adding work directly creates the desired product or service; API analysis, design, coding, and documentation are examples. section 2.11
  • Value-enabling work does not create the finished product directly but supports value-adding work under current conditions; acceptance and security testing are examples. section 2.11
  • Waste, or nonvalue-adding work, consumes resources without contributing anything customers value, such as waiting for a colleague. section 2.11

Improving an API value stream

Process mapping with value stream mapping techniques identifies wasteful activities to eliminate and value-adding activities to improve. This supports APIOps improvements for long API design lead times, documentation problems, and consistency problems. section 2.14

How Automating API Delivery covers it

How deep it goes
Defines value-adding, value-enabling, and waste categories with API and production examples, then connects them to process mapping.
Examples
Uses API analysis, design, coding, documentation, testing, reviews, work tickets, and waiting as classification examples.
What you can do after
Evaluate process activities and improve value-adding work using value stream mapping within APIOps transformation efforts.
How it connects
Links value-adding work with value-enabling work, waste, value stream mapping, APIOps, and A3 problem-solving.

Related concepts

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.