Please enable JavaScript.
Coggle requires JavaScript to display documents.
Lean Principles - Coggle Diagram
Lean Principles
Business involvement (get decision maker in the user requirement capture process)
Should converge business users’ objectives with IT technical knowledge of what is feasible
Prioritizes what they actually need i.e. their latent needs
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
Rapid iteration (to repeat the process fast until solution found and then move to next process)
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
reduce the risk of building the wrong system.
Uncovers latent needs
By focusing the team on just what user need most, it zap wasteful over engineering and gold-plated functionality.
Less code (avoid lengthy line of code, make it short and simple)
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 most rigorous testing cannot catch more than 50% of them. The more code, the more errors
Systems with less code are less buggy and cheaper to maintain
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