Please enable JavaScript.
Coggle requires JavaScript to display documents.
Lean Principles - Coggle Diagram
Lean Principles
Lean Idea #1 is Active Business Participation
The first lean principle is actively involving throughout the project. Prioritizes what hey actually need i.e. their latent needs. Should converge business users’ objectives with IT technical knowledge of what is feasible.
You do not need communication channels between IT and line functions when
business users are in the project team. They are the channel.
Combination of Business users and IT project team should have five characteristics
(CRACK):
Collaborative
Representative of users in their line function
Authorized to make decisions
Committed to delivering business value
Knowledgeable of their line function’s operations and business processes
Lean Idea #3: Less Code
to reduce the amount of software code in system.
Every line of code explicitly justified with business objectives
The less code principle bakes quality in and curbs costs in two ways:
Software with more code is buggier
The cost of fixing an error is about one hundred times greater after the software has been deployed.
(For example, Toyota’s 2009 braking software glitch cost the company around $10 billion in repair costs.23)
Historical data shows that an average programmer makes 10-15 errors in every 100 lines of code.
Even the most rigorous testing cannot catch more than 50% of them. The more code, the more error.
Less code lowers upfront development costs, which run between $15 to $40 per line of code.
Implemented using the 80/20 rule and short iterations
Lean Idea #2 is Short Iterations
The second lean principle is to do the project in a series of iterative sprints of two to
six weeks each.
Series of iterative sprints, 2-6 weeks apart
Each iteration hands users a crude but functioning
system with small subset of functionality
Integrally engage business users in a two-way conversation(a constructive conversation with the project team)
Marathon - many sprints (This analogous to
breaking a marathon into a series of 100m sprints)
Short iteration increase an IT project’s likelihood of delivering business benefits in 2
ways:
. Clears misunderstandings earlier - cheaper to fix
By clearing up misunderstanding earlier when there are cheaper to fix, they reduce
the risk of building the wrong system
Uncovers latent needs
Aps wasteful overengineering and gold-plated functionality
By focusing the team on just what user need most, it zap wasteful overengineering
and gold-plated functionality