evolution of the software development process at digital natives
DESCRIPTION
TRANSCRIPT
Evolution of the SW Development at Digital Natives
created byZsolt Fabó[email protected]: @ZsoltFabok
October 25, 2011 @Agile community, Cluj Napoca, RO
kaizen WIP kaikaku flow value
stream mapping visualize work flow cycle time lead time throughput TPS build failed CFD
reference: http://alistair.cockburn.us/Oath+of+Non-Allegiance
The Origin
photo: http://softwarecreation.org/2009/reliable-software-development-process-the-toyota-way/
Kanban - X
photo: http://blog.jonasbandi.net/2009/09/passionate-developer-i-do-like-my.html http://thepaisano.wordpress.com/2008/03/03/free-microsoft-project-clone/
The Traditional Way
Visualize the Workflow
Limit the Work in Progress
Measure and Manage Flow
lead time
cycle time
working time
queued time
Now we know where we are now: visualized and measured
We want to be better (quality) and faster
Lean principles:● Respect for People, Continuous Improvement
(kaizen)
Last two Kanban principles:● make process policies explicit,
improve collaboratively
Kanban is a method for development with a set of principles! Kanban
○ doesn't exist alone○ requires an existing process
+or
or
or
The first steps...
more columns
tasks
user stories
goal
FAIL: WIP limit
Our company board
new columns: deployment on staging and production
we still have tasks
revised deployment columns
new deployment strategy
two verification columns
FAIL: WIP limit
FAIL: new deployment strategy
Continuous integration build blocked everything
build failed (cont. integration)
Our SLA "door" + our detective board
reference: http://www.zsoltfabok.com/blog/2011/09/our-detectives-blackboard/
A post-it
Our Current Board
Thank you very much for your attention!
For more check out our websites:http://digitalnatives.hu/http://zsoltfabok.com/
or follow us on Twitter:@dinaistwitting@ZsoltFabok