The document outlines lean software development principles aimed at minimizing waste and enhancing learning throughout the development process. Key elements include identifying waste such as unused code or excessive features, amplifying learning through rapid testing and prototyping, and fostering collaboration within teams. It emphasizes the importance of delivering value quickly while maintaining flexibility and open communication to adapt solutions as needed.

1. LSD
Lean Software
Development
Part I
(Waste less - Learn more)

2. Lean Principles
Eliminate
Waste
Amplify
Learning
Delay
Decision
Deliver
Fast
Empower
Team
Build
Integrity
See
Whole

3. Eliminate Waste
Do you see waste?
● Code not in production
● Docs Unused (Customer tests not PRDs)
● Extra features (Maybe, How it works)
● Task Switching (1@time)
● Waiting (staff, specs, merge, test, deploy)
● Motion (Time to answer, Interfaces)
● Defects (Impact*Time to detect)
● PM Bullsh*t (backlog, tracking, change auth)
Do you see value?

4. Amplify
Learning
Recipe vs McChicken
Feedback
● Test asap
● Customer/Business Tests vs PRDs
● User Requirements vs Demos
● Study tools vs Spike top 3 tools
● Prototype vs full system
Iterations (small batch, options, sync via demo)
● Plan, Commit, Support*
● Convergence
● Negotiable scope and go by priority
Synchronization
● Sync & Stabilize (Fast & Freq. builds & tests)
● Spanning Application (End to end)
● Matrix (Interfaces then subsystems)
Options-Based Dev. (vs sols; not choices, constraints)
● Develop Multiple Options (prototypes, spikes)
● Selection (spontaneously happens)
● Communicate Constraints (not 1 solution)
● Let the solution emerge (vs selecting one)

5. Quick feedback,
real customers.

6. Review
How would you recommend this summary?
prasun{DOT}j{AT}gmail{DOT}com