2. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
Pulse of the Situation: why do 38% of organizations frequently use Agile practices?
Change In
Organization
Priorities
Most Common Reasons for
Project Failure
Inaccurate
Requirements
Gathering
Change in project
objectives
Source: Pulse of the Profession PMI 2015
6. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
The Question: Do I have to use Agile or Waterfall?
Complicated
Simple
Complex
Anarchy
Far from certaintyClose to certainty
Chaotic
projects
Agile
projects
Technology
Waterfall
projects
Unknown
changing
Well-known
unchanging
Requirements
7. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
Why Agile?
Allows IT to respond quickly to changing business needs
Reducing the time between customer requests and delivery
Builds of only the software requested by customers
Avoiding deliveries of software with quality problems
Providing the flexibility to re-prioritize scope to meet
evolving needs
8. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
Lack of Project
Documentation
No awareness of
final product
No planning
Limited to Small
Projects
Reality
Lack of discipline
Cure-all role for
software challenges
Myths about Agile
Increased Collaboration reduces low value tasks
“divide and conquer” can be beneficial on large projects
better understanding of what they can expect to receive
Repetitive approach to implementing software
Agile might not be the best approach
Detailed planning is essential
10. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
Digital Banks & Agile
10
Service oriented
Architecture
Technological
enhancement
(i.e. transition
to OPEN)
Real Time
Analytics
Open Bank
(i.e. Ecosystems,
API)
Digital challenges in the Banks’ Agenda
Industrialization of the Agile methodology to foster 2 speeds
architecture approach
NEW
DEVELOPMENT
CULTURE
IT DIGITAL
ENHANCEMENT
Advanced
Analytics
Digital
marketing
& Branding
Multi-devicesMultichannel
Digitalized
Operations and
Processes
automation
11. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
Choosing the right methodology
AgileHybridWaterfall
CUSTOMER AVAILABILITY
CLARITY OF BUSINESS REQUIREMENTS
TECHNOLOGY COMPLEXITY
TIME TO MARKET
The drivers above are not equally weighted. It actually depends on the
individual project and circumstances
12. ConfidentialCONFIDENTIALConfidentialCONFIDENTIAL DRAFT
2 Different Case studies showing a different setup
Case 2 –Mobile app for Corporate relationship
management support
Case 1 – New Credit Origination and Post-
sales system
Projectsetup
Project
Scope
SegmentSize
Pure Agile
Agile for Front end
+
Waterfall for the Back end
New web application to support
relationship manager in the Presales
activity
Unique cross product Front end
+
overall technological enhancement
following SOA concept
CorporateRetail
Medium/>yearHigh/Multiyear
14. 1. Culture
Shift
2. Preparing
the Ground
3. Methodology
Agile adoption – A few things to keep in mind
change throughout all levels of
the organization
Transparency & direct
communication
Adequate sponsorship
Commitment from all the
stakeholders
Tools and Methods framework
Training
How to ensure
Successful Agile
Adoption