agile beyond software development by slava moskalenko
TRANSCRIPT
www.luxoft.com
Agile Beyond Software Development
Luxoft Agile Practice Webinar
By Vyacheslav Moskalenko
02 Oct 2015
www.luxoft.com
Introduction
Vyacheslav Moskalenko
Agile Coach at Luxoft
Professional Scrum Trainer at scrum.org
https://ua.linkedin.com/in/slavamoskalenko
www.luxoft.com
www.luxoft.com
Session Plan
Origins of the Lean movement
Value Stream Mapping
Lean Principles
Lean thinking
ICAgile session attendance code
Q/A
www.luxoft.com
Meet Tom
We’ve got new
initiative driven
by financial
regulator
Scarcity of
resources
Ongoing overhead
Tough deadlines
www.luxoft.com
Lean was born from hardship and survival
Free up scarce cash
Reduce costs while
enhancing quality
And very little time to do this
http://www.flickr.com/photos/jtcatbagan/2420624616/
www.luxoft.com
Toyota success with the Prius
Developed within 18 months.
Toyota used 150 engineers
during development.
A typical competitor will take 4
years
A typical competitor will use
600 engineers.
Source - National Center for Manufacturing Sciences report
Note: this includes designing
the Plant to produce it!!
www.luxoft.com
Lean Definition
"Lean," is a production approach that considers the expenditure of
resources for any goal other than the creation of value for the end
customer to be wasteful, and thus a target for elimination.
www.luxoft.com
Value Stream Mapping
What does it mean? - Tom asked the Lean\Agile Consultant
OK, let’s visualize the flow from idea to production first
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
I400 fp
Time-to-market = 400 fp per 640 daysBusiness
UnitClients
1 day 5 days
178 days
2 days
45 days
2 days
30 days
120 days
120 days
130 days
7 days
I500 fp
I700 fp
I10 kloc
I3 Release
1 day 6 months 5 months 8 months 7 weeks 2 weeks
Target for elimination
www.luxoft.com
Lean principles
Eliminate waste
Amplify learning
Decide as late as possible
Deliver as fast as possible
Empower the team
Build quality in
See the whole
www.luxoft.com
Principle #1. Eliminate waste
Over-production
Waiting, delay
Handoff
Extra processing, relearning, reinvention
Partially done work (WIP)
Task switching
Defects
Not used people’s potential
Knowledge and information scatter or loss
Wishful thinking
www.luxoft.com
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
Business
UnitClients
1 day 5 days
178 days
2 days
45 days
2 days
30 days
120 days
120 days
130 days
7 days
I400 fp
I500 fp
I700 fp
I10 kloc
I1 Release
Lean thinking. Where is waste in the flow?
Developer is doing another task (Task Switching) – 13d
Developer is waiting for spec clarifications (Handoff) – 20d
Developer is waiting for design approval (Waiting) – 10d
Developer is fixing the defects (Defects) – 30d
Bureaucracy (Extra processing) – 100d
Slow internal communications – 28d
Overloaded BAs (Task switching) – 50d
www.luxoft.com
Principle #2. Amplify Learning
Feedback!!! Feedback!!! And Feedback!!!
Let developers learn the business context
and the current processes
Let your business to see an incremental
progress of the working software
Regular Inspect and Adapt sessions would
help you to get faster feedback on the
system weaknesses
Kaizen = DNA
www.luxoft.com
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
Business
UnitClients
1 day 5 days
178 days
2 days
45 days
2 days
30 days
120 days
120 days
130 days
7 days
I400 fp
I500 fp
I700 fp
I10 kloc
I3 Releases
Lean thinking. How do we communicate?
www.luxoft.com
Principle #3. Decide as Late as Possible
Just-in-time
Pull system
Bottom-up decisions
Go and see
I think the most important feature of the TPS is the
"Just-In-Time" (JIT) concept. This is the concept of a
system to make a product that is needed at the right
time, in the right quantity. Many books just emphasize
kaizen but JIT is the central part of the TPS.
Yasuhiro Monden,
Author of TPS
www.luxoft.com
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
Business
UnitClients
1 day 5 days
178 days
2 days
45 days
2 days
30 days
120 days
120 days
130 days
7 days
I400 fp
I500 fp
I700 fp
I10 kloc
I3 Releases
Lean thinking. How to reduce overhead?
The size of requirements
shouldn’t grow with each
new phase, ideally it should
decrease
Product Owner who
can decompose
business idea into
smaller and prioritized
units
Reduced release cycle as
huge increments much
harder to test
Pure efforts = 260 days per 400 fp
www.luxoft.com
Principle #4. Deliver as fast as possible
Scrum or Kanban
Cross-functional teams
Limit WIP
www.luxoft.com
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
Business
UnitClients
1 day 5 days
18 days
1 day
5 days
3 days
10 days
10 days
5 days
10 days
7 days
I100 fp
I80 fp
I50 fp
I0.7 kloc
I1 Release
Lean thinking. How to deliver sooner?
Product Backlog ManagementExtract MVP Simplify process
Time-to-market = 100 fp per 75 days
www.luxoft.com
Principle #5. Empower the Team
All errors and mistakes are due to the system within which people work rather
than to individuals themselves
“Beer game” study. Peter Senge's “The fifth discipline”
www.luxoft.com
Lean thinking. How optimize workload?
Time-to-market = 50 fp per 31 days
Wish listBusiness Value
AnalysisAnalysis,
Development, TestingDeploy
Business
UnitClients
1 day
4 days
10 days
5 days
10 days
I
100 fp
I50 fp
I1 Release
1 day
www.luxoft.com
Principle #6. Build quality-in
www.luxoft.com
Technique Time to detect problem
Pairing Seconds
Test Driven Development Seconds to minutes
Co-location Seconds to minutes
Continuous Integration ~20 minutes to a couple
hours
User Stories A couple days
Timeboxed development 1 – 4 weeks
Small releases 1 – 2 months
Lean Thinking. How to improve quality?
www.luxoft.com
Wish listBusiness Value
AnalysisAnalysis,
Development, TestingDeploy
Business
UnitClients
1 day
4 days
1 day10 days
5 days
10 days
I
100 fp
I50 fp
I1 Release
Lean thinking. What metrics do I have?
Time-to-market = 50 fp per 32 days
Process effectiveness = 22 / 32 = 0.68
Before: Time-to-market = 700 fp per 620 days
Before: Process effectiveness = 260 / 620 = 0.4
www.luxoft.com
Principle #7. Optimize The Whole
Where is waste in the flow?
How do we communicate?
How to reduce inventory?
How to deliver sooner?
How optimize workload?
How to improve quality?
What metrics do I have?
www.luxoft.com
Agile Beyond Software Development
Wish list Funding/Chartering AnalysisDevelopment &
TestingUser acceptance Deploy
I400 fp
Business
UnitClients
1 day 5 days
178 days
2 days
45 days
2 days
30 days
120 days
120 days
130 days
7 days
I500 fp
I700 fp
I10 kloc
I3 Release
AgileAgile + Lean
www.luxoft.com
Recommended Materials
Manifesto for Agile Software Development http://www.agilemanifesto.org/
www.luxoft.com
Available Trainings and Workshops of Luxoft Agile Practice
ICAgile Certified Professional - Agile Fundamentals https://icagile.com/icagile-certified-professional
ICAgile Certified Professional - Business Value Analysis https://icagile.com/icp-business-value-analysis
ICAgile Certified Professional - Agile Team Facilitation https://icagile.com/icp-agile-team-facilitation
Professional Scrum Master https://www.scrum.org/Courses/Professional-Scrum-Master
Management 3.0 https://management30.com/events/two-day-course/
Custom Workshops:
• Coaching and self-coaching;
• Agile project management;
• Agile project metrics;
• Motivation models;
• Feedback gathering;
• etc.
www.luxoft.com
Way Forward – ICAgile Certified Professional
ICAgile Certified Professional – Agile Fundamentals
Details - https://icagile.com/icagile-certified-professional
Registration
- For Luxoft employees
https://inthr.luxoft.com/IntHRWebApp/aspx_PTC/CreateRequestInternal.aspx?Course=SDP-031
- For non-Luxoft – http://www.luxoft.com/agile/icagile-certified-professional-icp/#request
www.luxoft.com
More Information
http://www.luxoft.com/agile
http://blog.luxoft.com/agile
https://sentinel2.luxoft.com/sen/wiki/display/AGLP/About+Us (Luxoft employees only)
My personal contacts:
https://ua.linkedin.com/in/slavamoskalenko
www.luxoft.com
THANK YOU