1. iZenBridge
Pull Planning, Lean
& Kanban
Saket Bansal , PMP® , PMI-ACP®
iZenBridge Consultancy Private Limited
© 2013 iZenBridge | CONFIDENTIAL

2. Agenda
• Lean Software
Part 1 Development Principles
Part 2
Part 3
• Pull System
• Pull System in Action
© 2013 iZenBridge | CONFIDENTIAL

3. The 7 Principles of Lean Software Development
•
•
•
•
•
•
•
Eliminate Waste
Build Quality In
Create Knowledge
Defer Commitment
Deliver Fast
Respect People
Optimize the Whole
© 2013 iZenBridge | CONFIDENTIAL

4. Eliminate Waste
Manufacturing
Software Development
In-Process Inventory
Partially Done Work
Over-Production
Extra Features
Extra Processing
Relearning
Transportation
Handoffs
Motion
Task Switching
Waiting
Delays
Defects
Defects
© 2013 iZenBridge | CONFIDENTIAL

5. Build Quality In
Preventing defects
Proactive Quality Assurance
Test First Approach
© 2013 iZenBridge | CONFIDENTIAL

6. Create Knowledge
 Team Engagement
Wiki
Kaizen
© 2013 iZenBridge | CONFIDENTIAL

7. Defer Commitment
© 2013 iZenBridge | CONFIDENTIAL

8. Deliver Fast
© 2013 iZenBridge | CONFIDENTIAL

9. Respect People
© 2013 iZenBridge | CONFIDENTIAL

10. Optimize The Whole
Inventories
•Hide errors in the process
•Hide misunderstandings
•Hide poor design
•Hide bugs..
© 2013 iZenBridge | CONFIDENTIAL

11. A Holistic View
Business
Management
Delivery
© 2013 iZenBridge | CONFIDENTIAL

12. forum.iZenBridge.com
© 2013 iZenBridge | CONFIDENTIAL

13. Agenda
• Lean Software
Part 1 Development Principles
Part 2
Part 3
• Pull System
• Pull System in Action
© 2013 iZenBridge | CONFIDENTIAL

14. It’s all about Scheduling !
© 2013 iZenBridge | CONFIDENTIAL

15. How to Schedule ?
© 2013 iZenBridge | CONFIDENTIAL

16. Push Sheduling
ES
ES
Analysis ,
Feature 1
Develop
Feature 1
ES
Test , F1 &
F2
Start
ES
ES
Analysis ,
Feature 2
Develop
Feature 2
© 2013 iZenBridge | CONFIDENTIAL
End

17. Challenges in Push Sheduling
© 2013 iZenBridge | CONFIDENTIAL

18. Re-Planning ….
• The old schedule was optimal based on old assumptions.
• The new schedule should be optimized based on the new
assumptions.
• Managers, based on their personal knowledge, decide the next
action.
© 2013 iZenBridge | CONFIDENTIAL

19. Pull Scheduling
© 2013 iZenBridge | CONFIDENTIAL

20. Toyota’s “Thinking Production System”
“Under a ‘push’ system, there is little opportunity for
workers to gain wisdom because they just produce
according to the instructions they are given,” he
says. “In contrast, a ‘pull’ system asks the worker to
use his or her head to come up with a manufacturing
process where he or she alone must decide what
needs to be made and how quickly it needs to be
made.”
Source http://www.toyotageorgetown.com/tpsoverview.asp
© 2013 iZenBridge | CONFIDENTIAL
Teruyuki
Minoura

21. Pull Sheduling
© 2013 iZenBridge | CONFIDENTIAL

22. forum.iZenBridge.com
© 2013 iZenBridge | CONFIDENTIAL

23. Agenda
• Lean Software
Part 1 Development Principles
Part 2
Part 3
• Pull System
• Pull System in Action
© 2013 iZenBridge | CONFIDENTIAL

24. Pull Scheduling for Software Projects
Visualize the Flow ….
Ready
Develop
Test
Done
Cycle Time
Limit WIP
Explicit
Policies
1. Code
2.Integrate
3.Update
Design
© 2013 iZenBridge | CONFIDENTIAL
1. Test XYM
1. Migrate /
Upgrade

25. System like Airport
© 2013 iZenBridge | CONFIDENTIAL

26. Just in Time
•
•
•
•
Don’t build features that nobody needs right now
Don’t write more specs than you can code
Don’t write more code than you can test
Don’t test more code than you can deploy
© 2013 iZenBridge | CONFIDENTIAL

27. Kanban
•
•
•
•
Self-directing
Details are on Card
The kanban cards tell developers what to do
Status is visible at a glance
© 2013 iZenBridge | CONFIDENTIAL

28. Kanban Board
Analyze (3)
Develop (5)
Analyze
Feature
Feature
Ready
for
Release
Accept (3)
Ready
(5)
Dev
Feature
Feature
Feature
Feature
Ready for Dev
Ready for
Accept
Feature
Feature
Feature
Feature
Feature
Feature
Feature
Columns For Each Work Type
Feature
Urgent
Criteria
•Design Complete
•Acceptance Test Case
Done
•UX Input Ready
•Code Complete
•Source checked In
•Unit Tests Green
•Build Succeeds
•Acceptance tests
Green
•PO Acceptance
© 2013 iZenBridge | CONFIDENTIAL

29. Information Radiators / Visual control
• Management by sight.
• Must be able to see
•
•
•
•
What is going on
What needs to be done
What problems exist
What progress is being made
• Work cannot be self-directing without appropriate visual
controls
• Examples: Lists of problems, Ideas for improvements,
Candidates for refactoring, Progress made
© 2013 iZenBridge | CONFIDENTIAL

30. Daily Meeting
•
•
•
•
Cards alone are not enough
A regular brief meeting helps make work self-directing
The daily team meeting should be short (15 minutes)
Everyone on the team should be there
© 2013 iZenBridge | CONFIDENTIAL

31. forum.iZenBridge.com
© 2013 iZenBridge | CONFIDENTIAL

32. Agenda
• Lean Software Development
Principles
Part 1
Part 2
Part 3
• Pull System
• Pull System in Action
© 2013 iZenBridge | CONFIDENTIAL

33. Stay Connected
Saket.Bansal@iZenBridge.com
www.iZenBridge.com
forum.iZenBridge.com
Youtube
LinkedIn Group
www.youtube.com/izenbridge
PMI-ACP: Agile Certification
Made Easy
© 2013 iZenBridge | CONFIDENTIAL