lean for project agility - kanban way

kanbanway.com | @kanbanPM

Lean For Project Agility Nov 18, 2014 Charan Atreya, MBA, PMP, LSSBB

http://kanbanway.com

mpug.comkanbanway.com | @kanbanPM



Why Lean• Exceed customer expectations • Improve Quality • Reduce Schedule • Improve Productivity & Throughput • Reduce Costs • Scale agility



DefinitionLean - Persistently identifying ways of adding value to customer, eliminating waste and improving continuously every day, by everyone through system thinking !Value add - process that changes the product or service that the customer is willing to pay for !Agility - Deliver value quickly, with high quality, with regular cadence



Lean - 4 Steps• Identify value flow • Structure teams to reduce or eliminate handoffs • Create a PULL process to complete work • Aggressively watch out for non-value added activities and eliminate them !!



Scenario of a flow



What’s wrong with this?

• Many hand-offs • Work flows back • Increased duration • Quality?



Scenario of a flow

Effort Duration

Effort Duration

Effort Duration

Effort Duration

Effort DurationEffort Duration

Wait Wait

WaitWait

WaitWait

Wait

Wait



Where do we begin• Measure time from start to delivery • Work aggressively reduce the duration

• Total Duration = Actual time to do the work (value time) + Hand-offs: wait time (waste)



Lean - Create Value Stream

Customer Request

Review & Approval

Detailed Requirements

Assessment and Design Development QA Production

Avg. Value Time (Effort) 10 min 15 min 60 min 30 min 10 hrs 2 hrs 30 min 14.42 hrs

Requests are viewed and approved weekly

Wait for a PO/BA to document requirements

Wait for an architect Wait for developer/s

Wait for staging and QE

Wait for deploy to production

Avg. Wait Time (Waste) 1/2 week 1 week 2 weeks 3 weeks 2 days 3 weeks 392 hrs

Process Efficiency = Avg. Value Time (Effort)Avg. Wait Time (Waste)

= 3.68%



Lean - Create Value Stream

Project Request

Create Charter

Capture Requirements

Design Solution

Build Solution QA Production

Avg. Value Time (Effort) 10 min 5 hrs 1 wk 1 wk 3 wks 1 wk 1 hr 246 hrs

PMO reviews project requests monthly

Wait for a PO/BA to document requirements

Wait for an architect Wait for developer/s

Wait for staging and QE

Wait for deploy to production

Avg. Wait Time (Waste) 2 week 2 weeks 2 weeks 3 weeks 2 days 6 weeks 616 hrs

Process Efficiency = Avg. Value Time (Effort)Avg. Wait Time (Waste)

= 16.4%

Avg. wait within process 1 wk 4 wks 5 wks 8 wks 4 wks 880 hrs



Where do we begin• Measure time from start to delivery • Work aggressively reduce the duration

• Total Duration = Actual time to do the work (value time) + Hand-offs: wait time (waste)



Eliminate hand-offsCross-functional Functional

Product Technology



Eliminate hand-offs

Define your process for optimized flow before deciding on structure



Flow Simulation



Ways work gets to teams



What are your teams working on?Project tasksMaintenance tasks

IncidentsProblems

Service Requests

PlannedUnPlanned



Visualize work as queuesFlow of work

Type of work

(10)(12)(15)



Visualize work as queues

Image: http://www.infoq.com/articles/agile-kanban-boards

Image: http://brodzinski.com/2010/02/kanban-board-revisited.html


http://www.infoq.com/articles/agile-kanban-boards

http://brodzinski.com/2010/02/kanban-board-revisited.html

http://www.infoq.com/articles/agile-kanban-boards

http://brodzinski.com/2010/02/kanban-board-revisited.html


Ponder ThisLimit Work-in-progress for faster flow

http://www.slideshare.net/ourfounder/personal-kanban-101


http://www.slideshare.net/ourfounder/personal-kanban-101


WIP, Throughput & Flow



Traditional vs Lean Thinking• Focus on maximizing utilization • “Busyness” • Schedule driven; PUSH system

for work completion • Low throughput and productivity

• Focus on maximizing throughput • System Productivity • Teams PULL work as capacity

becomes available • High throughput and productivity


mpug.comkanbanway.com | @kanbanPM




Lean Projects• Create value stream of project processes

• Eliminate non-value added steps • Impact: Reduction in costs & schedule

• Visualize and limit WIP • Establish a Kanban board • Impact: Tasks finish faster, high team morale,

reduced schedule • Optimize flow



Thank YouLean for project agility Nov 18, 2014 Charan Atreya [email protected] @kanbanPM


mailto:[email protected]

lean for project agility - kanban way

Documents