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
they actually need i.e. their latent needs and 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
A lean approach assumes two things:
Business users can’t articulate an IT project’s requirements. IT team must engage
with business users to discover their latent needs.
Success only in their eyes. The requirements will change over time and the
project is successful only if they find it useful.
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.
Each iteration hands users a crude but functioning
system with small subset of functionality
integrally engage bussines users in a two way conversation
Marathon => Many sprints
Short iteration increase an IT project’s likelihood of delivering business benefits in 2
ways:
Clears misunderstanding earlier <= Cheaper to fix
Uncovers latent needs
Lean Idea #3: Less Code is 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
Less code lowers upfront development costs, which run between $15 to $40 per