Kanban and Iterationless Working

Kanban & iterationless

workingKerry Buckley, 20 January 2010

Iteration

In the beginning was the waterfall

PlanPlan DesigDesignn

ImplImpl TestTest DeliveDeliverr







Why iterations?

XP: iteration

“A one- to four-week period. At the beginning, the customer chooses the stories to be implemented in the iteration. At the end the customer can run their functional tests to see if the iteration succeeded.”

Scrum: sprint

“A short burst of work lasting approximately 30 days during which an executable and other deliverables are built by an engineering team, as indicated by the assigned backlog.”

Agile

“ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

Agile

“ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

Learning from Lean

Waste (無駄 )

• Overproduction

• Waiting

• Transporting

• Inappropriate Processing

• Unnecessary Inventory

• Unnecessary or Excess Motion

• Defects

Waste (無駄 )• Overproduction – Extra Features

• Waiting – Waiting, Including Customers

• Transporting – Handoffs

• Inappropriate Processing – Extra Steps

• Unnecessary Inventory – Backlog; Undeployed Code

• Unnecessary or Excess Motion – Finding Information

• Defects – Defects Not Caught by Tests

Kanban看板

Push

AA BB

Pull

AA BB

Waste in Iterations

PrioPrio PlanPlan ImplImpl ImplImpl ImplImpl AccepAcceptt

DeliveDeliverr

ImplementImplement ImplImpl

ImplImpl ImplImpl Impl (oops)Impl (oops)

WTSTTCPW?

PickPick ImplImpl AccepAcceptt

DeliveDeliverr


DeliveDeliverr


DeliveDeliverr

AccepAcceptt

ReworReworkk

AccepAcceptt

DeliveDeliverr

PickPick ImplImpl

Our first attempt

Retrospection

•WTF does that card mean?

•‘Done’ stories not being deployed

•Missing regular celebration of completion

•Unwieldy backlog

•Can get away with very little estimation

Iteration two!

Estimation and tracking

Advantages

Disadvantages

end

Technology

Kanban and Iterationless Working