Lean principle
A lean principle is an approach to delivering value through efficient flow, reduced waste, and continuous improvement.
Automating API Delivery
Lean thinking is a management and improvement approach that maximizes customer value while minimizing waste and pursuing continuous improvement.
- How it is used
- Guides APIOps workflow improvements toward valuable, high-quality APIs delivered with fewer resources and less waste.
- How deep it goes
- Defines five principles and applies value assessment to process maps, emphasizing conceptual improvement methods rather than tool configuration.
- Examples
- Uses an API delivery process map and an A3 problem-solving sheet as concrete improvement artifacts.
- What you can do after
- Practice/perform it by mapping API delivery, identifying non-value-adding activities, and assessing proposed improvements with colleagues.
Shipping Go: Develop, deliver, discuss, design, and go again
Lean manufacturing is a production approach that minimizes waste and work not directly contributing to customer value.
- How it is used
- Frames lean manufacturing as a foundation for creating software efficiently while responding to customer demand.
- How deep it goes
- Introduces lean's industrial roots and customer-feedback rationale, but does not detail specific techniques.
- Examples
- Uses an airplane designed for a ten-mile trip to show why effort should match the actual need.
- What you can do after
- Evaluate how much effort to invest by clarifying the customer's actual need before building.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains lean principle →
Related concepts
- wasteuses · Waste is activity or resource consumption that does not contribute useful value to an intended product, process, customer, or organizational outcome.
- value streamuses · A value stream is the complete sequence of activities, decisions, handoffs, and information flows through which work creates and delivers value to a customer or user.
- behavior-driven developmentused by · Behavior-driven development is a collaborative software practice that specifies and validates expected behavior through human-readable examples meaningful to technical and nontechnical stakeholders.
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.