agile day 2013 - agile experience, between successes and failures [en[
DESCRIPTION
This slides have been presented at the agile day 2013, where I exposed my agile experience focusing on scrum methodologies. This presentation was focused on which key changes we tried (with more or less success) to adapt our way of working to the different project characteristics (development, maintenance, etc..).TRANSCRIPT
Esperienze di vita vissuta agilmente tra successi e
fallimentiLuca Foppiano
The Journey
2009
2011
2012
2013now
2009 - 2011 ETL Platform
2009
2011
2009 - 2011 ETL Platform
2009
2011
National patent offices
Platform
CN UK ITUS … DBs
100% Development!!
SCRUM by the book !
Patent business challenging !
Limitation were around the team
Deployment
Platform
CN UK ITUS …
Plat CN UK ITUS
TEST INTG UAT OSA PROD
2 weeks
‘Agile’ deployment
TEST I0 PROD
Platform
CN UK ITUS …TEST INTG UAT OSA PROD
< 1 week
3 days
x
Batch processing: No UAT
Discover your boundaries
What is not agile?
What should be improved?
What cannot be improved?
Focus on one thing!
2011 - 2012 ETL Platform (2)
2011
2012
~100-150 processes in Production Maintenance mode 1 weeks iterations
Length of the sprint
Long sprints vs Short sprints
First experiment worth trying
Sync with the deployment circle
2012 - 2013 ETL Platform (3)
Full maintenance project
Running more than 200 country programs
SCRUM weak points
Doesn’t work well on maintenance project!
Small, frequent and unexpected tasks
Lack of protection from the management
Not respecting the planning invalidate the whole methodology
2012 - 2013 ETL Platform
Maintaining the normal SCRUM methodology was too difficult
Kanban principles applied to a SCRUM approach
Planning transformed to a ‘light planning’ of 15 minutes
It worked!
Continuous experiment
Experiment, experiment, experiment
Consider going outside your scope: e.g. KANBAN
Remove what doesn’t work
2013 - now Workflow system
2013 - now Workflow system
Platform
Workflow Data Access Layer
Firefox Extension
Goal: deliver new features on an existing
application
2013 - now Workflow system
Development mode
PRINCE 2 + SCRUM
No team
Skills not easily available on the market
Creativity as skill
2013 - now Workflow system
After 1 year of experiments:
~1 week focused sprint*
Peer programming as part of the process
WIP max 1 task per person
Retrospective
Retrospective
Retrospective is a key point.
Retrospective -> storming -> action points
Retrospective is the driver for continuous improvements.
Q/A
http://www.flickr.com/photos/45842803@N00/2747637336
Thank you
Some articles from me
http://blog.foppiano.org/2012/10/22/kanban-some-myths-and-truths/
http://blog.foppiano.org/2012/10/29/agile-2-kanban-vs-scrum-myths-and-truths/