A Startup Journey: Ad-hoc to Agile to Kanban

A Startup Journey Evolving from ad-hoc to agile to kanban Siddharta Govindaraj siddharta@silverstripesoftware.com

1. Ad-hoc to Agile

Extreme Programming Feature Driven Development Scrum Crystal Clear

What went well?

Delivered Software Incrementally

Good Cultural Fit

Mistakes

Not Enough Feedback

Not Looking End To End

Not Talking To The End User (The person who pays is not the end user!)

Not Limiting Work In Progress

Too Many Projects!!

Not Enough Feedback Not Looking End To End Not Talking To The End User Not Limiting Work In Progress Too Many Projects!!

1. Agile to Kanban

Sprint Planning Was Broken

Velocity Was Meaningless For Us (What is it anyway?)

Getting Rid Of Iterations

Decoupling Releases (and other events)

Setting WIP Limits (enabler to pull & stop-the-line)

Lead & Cycle Time

Cross-Pairing

Team Centric Model

Sprint Planning Was Broken Velocity Was Meaningless For Us Getting Rid Of Iterations Decoupling Releases Setting WIP Limits Lead & Cycle Time Cross-Pairing Team Centric Model

Agile + Kanban

Agile + Kanban Self Organisation Empowered Teams Engineering Practices

Agile + Kanban Flow, Limit WIP, Pull Eliminate Wasteful Activities Look At The Whole Picture

Questions? Siddharta Govindaraj siddharta@silverstripesoftware.com

http://blogs.agilefaqs.com	87
http://www.silverstripesoftware.com	60
http://toolsforagile.com	52
http://www.slideshare.net	1

A Startup Journey: Ad-hoc to Agile to Kanban

by Siddhi on Jan 25, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 200

Statistics

A Startup Journey: Ad-hoc to Agile to Kanban — Presentation Transcript