6. Customer-centric
Eliminate Waste
1. Over-production
2. Inventory
3. Over-processing (includes
extra processes), relearning
4. Hand-offs
5. Task-switching, motion
between tasks, interrupt-
driven multi-tasking
6. Waiting and Delays
7. Defects, testing/inspection
and correction at the end
8. Not using people’s full
potential: “working to job
title”, no multi-skill, no
multi-learning, no kaizen, …
9. Knowledge and information
scatter or loss
11. Feature Teams
Feature Teams Component Teams
Focus on multiple specializations Focus on single specialization
Share product code ownership Individual/team code ownership
Shared team responsibilities Clear individual responsibilities
Supports iterative development Results in ‘waterfall’ development
Exploits flexibility: continuous and broad
learning
Exploits existing expertise: lower level of
learning new skills
Requires skilled engineering practices –
effects are broadly visible
Works with sloppy engineering practices –
effects are localized
Provides a motivation to make code easy
to maintain and test
Contrary to belief, often leads to low-
quality code in component
Seemingly difficult to implement Seemingly easy to implement
Source: http://www.featureteams.org/
32. Remember Larman’s Laws
1. Organizations are implicitly optimized to avoid changing the status quo
middle- and first-level manager and “specialist” positions & power
structures.
2. As a corollary to (1), any change initiative will be reduced to redefining
or overloading the new terminology to mean basically the same as status
quo.
3. As a corollary to (1), any change initiative will be derided as “purist”,
“theoretical”, “revolutionary”, “religion”, and “needing pragmatic
customization for local concerns” – which deflects from addressing
weaknesses and manager/specialist status quo.
4. Culture follows structure.
http://www.craiglarman.com/wiki/index.php?title=Larman%27s_Laws_of_Or
ganizational_Behavior