a startup journey: ad-hoc to agile to kanban
DESCRIPTION
This presentation was given at Agile Bengaluru 2010.TRANSCRIPT
1. Ad-hoc to Agile
Extreme ProgrammingExtreme Programming
Scrum
Feature Driven Development
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 OrganisationEmpowered Teams
Engineering Practices
Agile + Kanban
Flow, Limit WIP, PullEliminate Wasteful ActivitiesLook At The Whole Picture
