This document discusses agility in the banking and financial services industry (BFSI). It introduces various agile methodologies and frameworks like Scrum, SAFe, XP, DSDM, and Kanban. It also outlines some of the challenges of adopting agile in BFSI, such as different divisions having different technologies, long turnaround times for permissions, and availability of business stakeholders. The document provides perspectives on balancing priorities like customer success versus processes, and faster time to market versus failure negation. It recommends thinking about goals, collaborating to define a new way of working, and propagating changes gradually, such as starting with a few practices or a pilot team. The appropriate agile practices depend on factors like project size and requirements stability

1. Be Agile. Be Enlightened!
Agile in BFSI

2. We will discuss…
• The Essence of Agility
• The Challenges
• Different perspectives of Agile adoption in BFSI
• IT projects vs Core Business
• Customer success vs Processes
• Faster time to market vs Failure negation
• Technology advances vs Mainframes
• No silver pills
• Summary

3. All Agile methods are necessarily Iterative, but not all Iterative processes are Agile
A Process…
A Framework…
SoWhat is Agile ??

4. PrinciplesandValues
Essence
Practices
Decor
AgileButs
Myths
The three aspects of Agility

5. SCRUM
DAD SAFe
XP
DSDM
Agile
Modelling AUP
Kanban
LESS
Agile Methodologies and Frameworks
Battlefield
Agility

6. The Dilemmas and challenges
Security and
CompliancesDifferent
Divisions,
Different
Technologies
Time to
propagate
changes to entire
system
Turnaround time
for permissions
Availability of
business
stakeholders
Outsourcing vs
Captive IT or a
mix??
Multiple
Vendors…

7. Agility in BFSI
Different perspectives

8. IT Projects vs Core Business
• IsAgility only for IT team………
• Well… No!!
• The philosophy applies everywhere,The rituals ( aka practices) may be different
• The practices may be different between IT and Core Business
• Let’s take an example…

9. Customer Success vs Processes
• Customers think and sometimes they would need us to go beyond what is in
the process
• So do we focus on Customer Delight or go always by the rule book ??
• That’s a tough call for management and the Product Owner

10. Faster time to market vs Failure Negation
• The market is always boiling…
• So do we focus on getting the newest features ( Indusind’sVideo call your branch, ICICI’s
open you account at home etc.)
• OR
• Do we play safe and make sure we have tested and tested everything so that we don’t
have to regret later

11. Technology
• Mainframes till rule the roost at the core of
most BFSI Infrastructure
• But the technology is changing
• The speed of upgrade also determines the turn
around time, a crucial entity for an Agile team

12. The bad news
• There are no silver pills
• Every organization, Every project, Every team is different
• So…You can’t have one solution available

13. But that doesn’t solve my
problem… I am still
stuck!!!!
No worries, Here is some help

14. Step 1:Think
• Why do we need to be Agile.The Goals..
• What targets ( aka KPIs) we are looking to improve…
• What is our timeline for a complete transformation

15. Step 2: Collaborate to decide the way of working
• Process definition workshops
• Brainstorming sessions and one-on-ones with key stakeholders
• Develop a transformation roadmap

16. Step 3: Propagate the change
• May be start with a town-hall where everyone is informed about the
expectation
• Then take it one step at a time…
• May be a few practices
• May be a pilot team
• And do measure the progress…regularly

17. That sounds good…
but which practices we may choose??

18. • Scrum
• Kanban
Small Development
Project, Known
Requirements
• SAFe or
LeSS
• Kanban
Large Development
Project, Known
Requirements
• Kanban
• Battlefield
Agility
BI & DW
• Kanban
• Modified
Scrum
Enhancements and
maintenance
• Agile
Modelling
• DSDM
MDM and Big Data
Analytics

19. Be Agile. Be Enlightened!
www.agivetta.com
info@agivetta.com