Using Kanban for continuous improvement
42
Using Kanban for continuous improvement in a growing software development company Jorge Ferrer Esther Sanz
Transcript of Using Kanban for continuous improvement
Using Kanban for continuous improvement
in a growing software development company
Jorge Ferrer Esther Sanz
2 Years journey of continuous improvement
end of2012
JAN2013
DISCOVERING Kanban as source of ideas Kanban seems a better fit than Scrum
INTRODUCING STRATEGIC ALIGNMENTIntroducing Product Management
JAN2014
CROSS-FUNCTIONAL TEAMSGrowing ownership
JUN2013
REDUCE VARIABILITY CHANGING POLICIESChanging Policies
APR2015
TEAMALIGNMENTOKRs, Guilds, New tools for communication
Open Source DevelopmentAgile influenceFast dev speed
There is no silver bullet“Kanban encourages diversity. You have permissions
to be different”
WHAT IS KANBAN FOR US?A methodology to drive continuos improvement
Evolve experimentallyIncrease collaboration and feedbackStatistics based prediction
Focus on QualityLack of quality ends up causing slow downs
VisibilityPromote work visibility and
transparency
Manage flowManage your value stream
Limit your workBalance Demand
Continuous Improvement
What is LIFERAY?
Continuous
Growth
CollaborationCulture
CompanyLos Angeles, 2004
17 offices, 2014
From 2000
Open SourceSoftware
Project
GARTNER: From Visionaries to Leaders
Niche Players! Visionaries!
Leaders!Challengers! Leaders
Visionaries
Challengers
Niche players
150 people working together
Engineers together with the collaboration of CommunityVery AGILE and PRODUCTIVE team
Seeking for talent all around the worldHIGHLY MOTIVATED and TALENTED People
Lean principleNatural Bottom-up approach
Liferay Engineering
Do all the improvement initiatives come from something not working as
expected?
IMPROVE OR DIE
“There are risks and costs to action. But they are far less than the long range risks of
comfortable inaction” John F. Kennedy
Goals in Engineering
Productive & agile environment
High quality product
Fun Development
Empower developers to
innovate
Transparency Responsive to Feedback
Does that sound familiar?
Kanban helps you to:Focus on Quality
Reduce work in progress
Attack sources of variability
Prioritize
Deliver often
Balance demand against throughput
Kanban maturity level
0"
1"
2"
3"
4"
5"Visualize""
Limit"WIP"
Manage"Flow"
Explicit"Policies"
Feedback"Loops"
Improve"CollaboraFvely"
Alignment vs Autonomy
Finding the right balance
low
low
high
high
Alignment
Autonomy
Hope someone is working on the river problem
Figure it out how
Build a bridge
We need to cross the river
We need to cross the river
Inspired by Henry Knieberg
Increasing strategic alignmentIntroducing a Product Management department
Communication
Strategic Feedback
New work flowAdded steps in the value stream
low
low
high
high
Alignment
Autonomy
Hope someone is working on the river problem
Figure it out how
Build a bridge
We need to cross the river
We need to cross the river
Inspired by Henry Knieberg
Increasing agility through autonomyCross-functional teams
Clear Responsibility
Define clear responsibilities for each team. They should have
full ownership of the products they work on.
Multidisciplinar
Organize teams which have all skills needed to
build the product: UX designer, developer,
tester, product manager, documentation.
Right controls in place
Define policies that help team members to
prioritize work and make informed decisions while still striving for the global
goals
low
low
high
high
Alignment
Autonomy
Hope someone is working on the river problem
Figure it out how
Build a bridge
We need to cross the river
We need to cross the river
Inspired by Henry Knieberg
The feeling of ownership is key to
drive improvements
Autonomy + Responsibility = OWNERSHIP
Strategic functionalities 2013
16%
39%
201421%
27,5%
2015
33%
FLOW EFFICIENCY
LEAD TIME (median)% Decrease in time
Flow efficiency = Work time / lead time (%)
Testing times has been reduced about 40% but we still have a clear bottleneck
Have you heard about local maximum?
Walking the valley of uncomfortable
Valley of uncomfortable
Investing in QualityLooking for a Sustainable pace
Focus on QUALITY
Beta Testers Community Program
Automated unit/integration test run on every Pull
Product Modularization
Code quality analysis tools
Improving visualization
Presentation to Joe Smith�30
Presentation to Joe Smith�31
Presentation to Joe Smith�32
Presentation to Joe Smith�33
Kanban maturity level
0"
1"
2"
3"
4"
5"Visualize""
Limit"WIP"
Manage"Flow"
Explicit"Policies"
Feedback"Loops"
Improve"CollaboraFvely"
0"
1"
2"
3"
4"
5"Visualize""
Limit"WIP"
Manage"Flow"
Explicit"Policies"
Feedback"Loops"
Improve"CollaboraFvely"
Remaining challenges
Reduce WIP
Leveraging slackPredictability vs Innovation
Cross-polination among cross-functional teams
Final thoughts
Challenge everything
Avoid ever lasting routines
Don’t freak out with metrics!
Change takes time
Engage people in changes
Listen to your team
Síguenos: @jorgeferrer
GraciasThanks
@esthersanzp
