Jumping over hurdles for agile adoption in banks () english
1. Jumping over hurdles for agile adoption
in banks
November, 2012
Zvonimir Križ, main coordinator in Application SW Division, PBZ
President of Agile Croatia
2. PBZ
• second largest Croatian bank
• part of Intesa Sanpaolo
• 10 bil EUR of total assets
• cca 500 people in IT
• cca 200 in app development
2
3. Three phases of agile adoption in PBZ
1. 2009 – Single Scrum team
2. 2010-2011 – Agile practices in multiple teams
3. 2012 – Agile is popping out of IT
Direct motive to give agile a try at the end of 2009 were problems on PBZ365 product.
We have identified following problems that possibly can be resolved by agile
development:
• we are doing too much overhead
• too much bugs
• unclear requests
• failure to meet deadlines
• unknown / unclear plans
• bureaucracy
• slow and inefficient communication
3
4. Phase 1: Scrum pilot project
We ran pure Scrum for 3 months, and then compared it to a previous 3 months.
Collected data (before and after) were from our issue management system which means
it's real.
The results were as follows:
1. Unplanned production releases dropped from 8 to 4. 50% better
2. Critical bugs in production dropped from 5 to 2. 66% better
3. Improvements raised from 9 to 29. 211% productivity boost
4. Improvements vs bugs from 1:2 to 2:1. Focus on business
5. Subjective evaluation of all team members and stakeholders were MUCH BETTER
4
5. Phase 2: Multiple teams practicing agile
Employed practices:
• iterations – 4 weeks at the beggining, now 2 weeks
• daily standups
• sprint planning
• sprint retrospective
• sprint demo (sprint review)
• prototyping (using Bootstrap)
• self-organized teams – biggest productivity boost
• continuous integration (but without unit tests )
• pair programming (for new developers and for code review)
• refactoring
But still no:
• Test Driven Development / Behaviour Driven Development
5
6. Phase 3: Agile is popping out of IT
• Agile estimating for a group-level project
• PMO made Scrum and Kanban "legal" in the following way
• Official PBZ methodology says: "Scrum framework as an extension of the methodology can be
applied only in the projects (and teams), where it is agreed with all stakeholders (particularly it
relates to business users and PMO)."
• PMO defined an action plan to introduce agile in PBZ
• For agile projects, it will function like this:
6
7. What was good and what was bad
GOOD
BAD
7
We had highly
positioned manager to
protect shift to agile
We just pushed agile
withot asking people if
they want it or not
We had no expirienced
consultants and started
withot education
We spent too much time
trying to convince
sceptics
8. Next steps
Contact me with any questions
E-mail: zvonimir.kriz@gmail.com
Twitter: @zvonekriz
LinkedIN: http://hr.linkedin.com/in/zkriz
Come to Agile Adria Conference April 22-23, 2013
http://agileadria.com
8