Please enable JavaScript.
Coggle requires JavaScript to display documents.
Lean Principles - Coggle Diagram
Lean Principles
Three foundational principles of all lean methods:
Active business participation
C-R-A-C-K Business Team Members
• Collaborative
• Representative of biz users
• Authorized to decide
• Committed to business value
• Knowledgeable
Short iterations
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
– Marathon many sprints
Clears misunderstandings earlier - cheaper to fix
Uncovers latent needs
Zaps wasteful over engineering and gold-plated functionality
less code
Bakes in quality and curbs costs in two ways:
Software with more code is buggier
– 100-150 errors/KLOC + 50% best-case bug squashing during testing
– Translation: A small (1 mil LOC) app with have 5,000+ bugs
– Bug fixing is 100 times costlier after deployment
Lesser code lowers upfront development costs ($15-$40/ LOC)
Implemented using the 80/20 rule and short iterations
Other lean-enabling ideas
Constant automated testing
Continuous integration–reduces integration glitches at the end
Lean or Waterfall?
waterfall
•Stable requirements
•Proven technologies
• e.g., infrastructure
large project
larger project always more challenged
small project
Success triples
if made smaller
ASSUMES
Business users can’t articulate an IT project’s requirements
Success only in their eyes
Lean Payoffs: Better, Faster, Cheaper
Active business involvement
build the right system
short iterations
build the right system
cheaper and faster
less code
cheaper and faster
bake quality in