What Lean Is and What it Isn’t
Cost of Delay. “If you only quantify one thing, quantify the Cost of Delay” – Don Reinertsen In a nutshell, the “cost of delay” is what it costs an organization in lost revenue, lost opportunity, increased risks, customer respect, etc., due to a delay in realization of value. Everyone knows intuitively that delays in software delivery impose some economic cost on the organization. But what exactly is that cost, and how do we measure it? Applying a combined Lean-Agile perspective, we can understand these costs better. More importantly, we can use the same perspective to improve the speed and reliability of software delivery, while making important choices about when you’ve delivered enough value.
The business Case for Agility. Agile is not just for the team anymore. Business can become more profitable while incurring less risk when they take Agile methods to the organization.
Minimum Business Increments (MBIs). It’s exciting to talk about startups and Minimum Viable Products. But more organizations are enhancing their existing products. Lean how the Minimum Business Increment is one of the most important Lean-Agile methods available.
The Value Stream
Mapping a Value Stream to a Kanban Board. In this short video, Al Shalloway describes the process of mapping a value stream to a Kanban board and why both are important in improving business-driven software development.
Leadership and Management. This references a key article that Lean Management is based on.
Improving Your Company’s Culture. This discusses how management is required to change culture.