Lean , Pull System & Kanban |iZenBridge

© 2013 iZenBridge | CONFIDENTIAL

iZenBridge

Pull Planning, Lean

& Kanban

Saket Bansal , PMP® , PMI-ACP®

iZenBridge Consultancy Private Limited


Agenda

Part 1

• Lean Software Development Principles

Part 2 • Pull System

Part 3 • Pull System in Action


The 7 Principles of Lean Software Development

• Eliminate Waste

• Build Quality In

• Create Knowledge

• Defer Commitment

• Deliver Fast

• Respect People

• Optimize the Whole


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


Build Quality In

Preventing defects

Proactive Quality Assurance

Test First Approach


Create Knowledge

Team Engagement

Wiki

Kaizen


Defer Commitment


Deliver Fast


Respect People


Optimize The Whole

Inventories

•Hide errors in the process

•Hide misunderstandings

•Hide poor design

•Hide bugs..


A Holistic View

Business

Management

Delivery


forum.iZenBridge.com


Agenda

Part 1





It’s all about Scheduling !


How to Schedule ?


Push Sheduling

Start

Analysis ,

Feature 1

Analysis ,

Feature 2

Develop

Feature 1

Develop

Feature 2

Test , F1 &

F2

End

ES

ES ES

ES

ES


Challenges in Push Sheduling


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.


Pull Scheduling


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

Teruyuki

Minoura


Pull Sheduling




Agenda

Part 1





Pull Scheduling for Software Projects

Ready Develop Test Done

Visualize the Flow ….

Limit WIP

1. Code

2.Integrate

3.Update

Design

1. Test XYM 1. Migrate /

Upgrade Explicit

Policies

Cycle Time


System like Airport


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


Kanban

• Self-directing

• Details are on Card

• The kanban cards tell developers what to do

• Status is visible at a glance


Kanban Board

Ready

for

Release

Urgent

Criteria

Analyze Ready for Dev Dev Ready for

Accept

•Code Complete

•Source checked In

•Unit Tests Green

•Build Succeeds

•Design Complete

•Acceptance Test Case

Done

•UX Input Ready

•Acceptance tests

Green

•PO Acceptance

Feature

Feature

Feature Feature

Feature

Feature Feature

Feature

Feature

Feature

Feature

Feature

Feature

Feature

Columns For Each Work Type

Ready

(5)

Analyze (3) Develop (5)

Accept (3)


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


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




Agenda

Part 1





Stay Connected

Youtube

www.youtube.com/izenbridge

LinkedIn Group

PMI-ACP: Agile Certification

Made Easy

[email protected]

www.iZenBridge.com


http://www.izenbridge.com/

Education

Lean , Pull System & Kanban |iZenBridge