liveBook · Manning

Waste

Waste is activity or resource consumption that does not contribute useful value to an intended product, process, customer, or organizational outcome.

How 2 Manning books explain it

Build High Value Software Systems

Work that creates no customer value and can be eliminated without harming delivery or its outcomes.

How it is used
Identifies avoidable effort in the path from customer request to working software so teams can improve flow rather than celebrate activity.
How deep it goes
Defines waste against customer value and necessary safeguards, then gives recognition patterns and a pull-request audit rather than a fixed classification.
Examples
Uses a delayed bug fix, build and review waits, and speculative AI-generated code to expose work beyond the requested change.
What you can do after
Practice/perform a pull-request audit that separates value, necessary protection, and avoidable effort before proposing a small system change.

Read how Build High Value Software Systems explains waste →

Automating API Delivery

Waste is process effort or elapsed time that does not contribute value to delivering the intended product or change.

How it is used
Identifies where an API delivery workflow consumes time without advancing customer value, so improvements target end-to-end performance.
How deep it goes
Classifies production activities and quantifies idle time with a worked activity-ratio calculation; does not specify an automated waste-detection tool.
Examples
Uses approval of a new API operation: 5.25 hours of work across 128 hours of elapsed time.
What you can do after
Diagnose/debug with a process map and activity ratio to find waiting that dominates an API change’s elapsed time.

Read how Automating API Delivery explains waste →

Also covered in

What to know first

Related concepts

Questions about waste

What is waste?

Waste is activity or resource consumption that does not contribute useful value to an intended product, process, customer, or organizational outcome.

Which Manning books explain waste?

Build High Value Software Systems and Automating API Delivery.

What should I know before learning waste?

Manning books that teach waste usually introduce backlog, cognitive load, CPU time and feedback first.

What kinds of waste are there?

Kinds of waste include unused skill and waiting waste.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.