Date post: | 07-Jul-2015 |
Category: |
Software |
Upload: | sunil-mundra |
View: | 170 times |
Download: | 0 times |
1
GETTING A PARTNER TO ADOPT AGILE
Sunil Mundra
Principal Consultant
CONTEXT
3
CONTEXT
CONTEXT
• The Client:
A mid-size Bank in Australia
• The Partner:
Financial Service Division of a
Global IT Conglomerate 4
CONTEXT
• The Client engaged with the Partner
to replace their Core Banking
Platform
• The Partner’s next generation product
was under development using
Waterfall, and the Client was most
likely the first bank to go live with this
product. 5
CONTEXT
• The Client Group’s Insurance division
had successfully undergone Agile
Transformation. The Bank had begun
following Agile in many areas since
past 2 years
• Client reluctantly agreed to Partner’s
Waterfall approach at the start of the
engagement
6
CONTEXT
• A few months into the engagement,
the Partner informed the Client that
the next version of the Product will
be delayed by a year
• The Client threatened to end the
relationship unless the Partner
adopted Agile for doing client specific
development work
7
CHALLENGES
CHALLENGES
Trust Deficit
9
CHALLENGES
Partner’s Pride
10
CHALLENGES
Barriers to
Communication &
Collaboration
11
CHALLENGES
Discomfort With
Continuous Visibility
& Transparency
12
CHALLENGES
‘Throw It Over The
Wall’ Mindset
13
LEARNINGS
LEARNINGS
Start Small,
Demonstrate Success
15
LEARNINGS
Cross Pollinate
People
16
LEARNINGS
Provide Continuous
Coaching
17
LEARNINGS
Involve In Entire
Delivery Cycle
18
LEARNINGS
Pick Your Battles
19
THANK YOU
s u n i l r m @ t h o u g h t w o r k s . c o m
QUESTIONS?
s u n i l r m @ t h o u g h t w o r k s . c o m