Embed Size (px)
Citation preview
Be Agile. Be Enlightened!
Agile in BFSI
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
All Agile methods are necessarily Iterative, but not all Iterative processes are Agile
A Process…
A Framework…
So What is Agile ??
Pri
nci
ple
s an
d
Valu
es
Essence P
ract
ices
Decor
Ag
ileB
uts Myths
The three aspects of Agility
SCRUM
DAD SAFe
XP
DSDM
Agile Modelling AUP
Kanban
LESS
Agile Methodologies and Frameworks
Battlefield Agility
The Dilemmas and challenges
Security and Compliance
sDifferent Divisions, Different
Technologies
Time to propagate changes to
entire system
Turnaround time for
permissions
Availability of business stakeholder
s
Outsourcing vs Captive
IT or a mix??
Multiple Vendors…
Agility in BFSIDifferent perspectives
IT Projects vs Core Business
• Is Agility 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…
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
Faster time to market vs Failure Negation
• The market is always boiling…
• So do we focus on getting the newest features ( Indusind’s Video 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
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
The bad news
• There are no silver pills
• Every organization, Every project, Every team is different
• So…You can’t have one solution available
But that doesn’t solve my problem… I
am still stuck!!!!
No worries, Here is some help
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
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
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
That sounds good…
but which practices we may choose??
• Scrum• Kanban
Small Development Project, Known Requirements
• SAFe or LeSS
• KanbanLarge Development Project, Known Requirements
• Kanban• Battlefie
ld Agility
BI & DW
• Kanban• Modified
ScrumEnhancements and maintenance
• Agile Modelling
• DSDMMDM and Big Data Analytics
