1. Lean for Scrum Teams
Savita Pahuja

2. Challenges
with Scrum
Teams
Scrum
Kaizen Lean
Waste
Removal
Limit
WIP

3. Scrum

4. Challenges
• Many stories remain incomplete
• Incomplete Testing
• Inability to handle the interruptions
• Estimation takes too long
• Lack of predictability of business value delivered
• Difficulties with distributed teams
• Inability to create the requisite cross-functional
teams

5. Measure Progress
0
10
20
30
40
50
60
70
80
90
100
S1 S2 S3 S4 S5 S6 S7 S8 S n
Velocity
Velocity

6. Kaizen

7. Lean

8. Lean

9. Lean in Software Development
1. Eliminate waste
2. Amplify learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build integrity in
7. See the whole

10. Eliminating Waste
Insufficient requirements
Slow / Poor Communication
Technical Debt
Unused code or features
Rework
Too Much detailed Requirements
Handoffs between teams

11. Apply Waste Removal in Scrum Teams
Waste Backlog
Writing unit tests after development
Less automation testing
Preparing requirements document
Sequence Diagram, Class Diagram etc
Manual Builds
Wait time because of dependency on other
teams

12. Limit Work in Progress
To DO In Progress Done
First Day of the Sprint

13. Limit Work in Progress
To DO In Progress Done
Middle of the Sprint

14. Limit Work in Progress
To DO In Progress Done
Last day of the Sprint

15. Lean Approach - Limit Work in
Progress
To DO In Progress
(3)
Done

16. Remove Delays in Workflow
Value Stream Map

17. Reduce Wait Times
Lead Time

18. Scrum within Lean-Thinking
Benefits
Focus on entire development cycle
Eliminate waste
Remove delays in the workflow
Limit WIP
Build quality in