Legacy financial organisations (viz. BFSI – Banking, Financial Services and Insurance enterprises) operate in a regulatory and high-risk environment. This session discusses some of the organisational dysfunctions such companies experience during their Agile transformational journey.

The session will help you understand and empathize with such dysfunctions and some possible mitigation patterns. Sample dysfunctions below:

  • There are multiple middle management layers which are redundant and mostly resistant to change.
  • Huge upfront planning and big-bang delivery model is practiced.
  • Rewards and Recognition of individual performances still exists.
  • Command and Control mode of working still exists. For example, Scrum teams do not have the liberty to conduct Retrospectives.
  • Business teams are not aligned with IT teams.

The speakers’ experience is accumulated over the years while working with multiple and large financial organisations across the globe.

 
1 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This session discusses patterns emerged from real experiences delivered in workshop style. My experiences of transformation at large and legacy financial enterprises combined with the participants’ experiences will be collectively brainstormed in a workshop format. This will also promote discovery of some of the topics unexplored in the industry today such as Agile in regulatory environment, Agile in bureaucratic organisations etc. There will be no or very few slides with more images than text thus triggering interactions rather than a one-way talk.

The overall session delivery will be based on ‘Brain Science Learning’ to create higher impact. 'Training from Back of the Room' techniques will be used to facilitate the workshop, so that the participants have real takeaways so that they can apply in their transformations.

Learning Outcome

  1. Challenges faced by legacy financial organisations during Agile transformations.
  2. What are the options to mitigate such challenges?
  3. Some case studies on how Fortune 500 organisations have emerged successful.
  4. A leader's perspective in a legacy organisational transformation.

Target Audience

Team members, Project Managers, Program Managers, Senior Leaders, Agile coaches, Scrum Masters, Program Executives, PMO, any curious member of the organisation.

Prerequisite

Nice to do but not mandatory: Interested participants can record responses to the following questions and bring to the session (This technique is called Scavenger Hunt):

  1. List down one financial enterprise which went through Agile transformation in last couple of years. (If data is confidential, then just write down indicative details such as country of enterprise, domain of business etc. Eg. Top retail bank in USA).
  2. Are you a member of the transformation journey? (Yes/No)
  3. List down one dysfunction you observed during the transformation.
schedule Submitted 3 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  2 weeks ago
    reply Reply

    Hi Suresh,

    Besides the points from Prasad I agree with there are few things in the proposal the caught my attention.

    Neither the outline or learning outcome discusses specifics on financial services but are rather generic. The points below is something you need to think thro' and update the proposal.

    1. This is a proposal focused on BFSI/FS industry - I just want to make sure that you are aware the audience at Agile India will be from various other industries. Your proposal might limit the number of people attending your session which is alright but the talk/content with specifics from your experiences is helpful
    2. Is this a workshop or a case study. I ask this because you've marked the proposal as case study while there are pre-reqs and the requirements for the session expect stationary/material necessary in a workshop.
      1. What if no one shows up without completing the pre-reqs? If this is important then help us educate how you intend to use the responses. 

     

    Best,

    Ravi

     

  • Prasad
    By Prasad  ~  3 weeks ago
    reply Reply

    Thank you Suresh for the proposal.. as year progresses we are seeing a level of maturity in our participants. In the current proposal I am not seeing any significant learning or take away.  Why don't you emphasis more on patterns / approach through which you have transformed legacy organisation.. how did you knew it is transformed, what is the success look like ..

    cheers

    P


  • Liked Gaurav Rastogi
    keyboard_arrow_down

    Gaurav Rastogi - Agile Vendor Management Manifesto

    45 Mins
    Talk
    Executive

    Want to discuss and share the Manifesto which a group of coaches including myself have written.

    Please refer to www.vendormanagementmanifesto.org for details

    1.1 The Governance
    The delivery team is governed by contracts. There are 2 types of contract we will be considering
    •The Master Contract : This is a contract signed between the Customer and Supplier Management teams and governs the entire set of Scrum projects being executed.
    •The individual work order level contracts: This is a contract which will govern the detailed work to be done by teams.

    This manifesto will take into account both the type of contract

    1.2 The Roles
    The roles covered under this Manifesto are as follows
    The Customer Management This is the management team of the customer
    The Vendor Management Team Vendor Management team will work on behalf of the Customer Management team in preparing the contract and negotiating the same with the Supplier’s management
    The Team The team will consist of multiple Scrum teams working on the projects governed under the Master Contract. They will end up working under the individual Work Orders signed up with the customer.
    The Supplier Management The Supplier Management team will negotiate the terms and conditions of the Master Contract of the contract along with the The Customer Management team (and the Vendor Management team).

    1.3 The Objective of this Manifesto

    The Objective of this Manifesto is to define guiding principles around the Customer-Supplier working environment with regards to working on Scrum projects. The assumptions made are
    •The environment is customer-supplier (i.e. an outsourced environment)
    •The environment is distributed and may not be co-located
    •The environment involves multiple vendors

    The Customers and Suppliers are integrated elements of a working environment in a project. The Customers and Suppliers will work together with a common goal and that is “Producing Value for the End Customer”. This manifesto supports the Agile Manifesto Value “Customer Collaboration over Contract Negotiation”.

    There are 12 principles which will support the Agile Value and are presented below in a format of Left over Right. The items on the left are valued more than the ones on the right.

  • Liked Gaurav Rastogi
    keyboard_arrow_down

    Gaurav Rastogi - Beingh Hi-Touch in Hi-Tech World

    45 Mins
    Tutorial
    Beginner

    It is very unfortunate that we are becoming Hi-Tech every single day at the cost of Being Hi-Touch.

    Recently i took a photograph of my family sitting in a room and not talking to each other but busy with their gadgets,This Paper is to help propagate the Agile Manifesto value "Individuals & Interactions over Process & Tools"

    to provide techniques and Help Leaders, Coaches, Change Agents, Team members to understand people better in their teams and work with them more effectively. This talk is based on the DISC human behaviour model.

    As a saying is It's not what you say It's what they listen and understand Matters.

  • Liked Sathya Jayapaul
    keyboard_arrow_down

    Sathya Jayapaul / Vikas Goel - New Ways of Working for Legacy Mainframes Systems : A journey

    20 Mins
    Experience Report
    Intermediate

    This presentation is on the journey of Agile and DevOps transformation within the Core Banking & Payments division in RBS. This division forms the heart of the banking and Payments technology of RBS. The division has around 25 platforms supporting 150+ applications with most of their technology base being IBM mainframes.

    These are critical platforms as 1 in 4 of all payments in the UK are processed by RBS' payment systems, with the total value of RBS UK & International payments in 2016 being around GBP 55 trillion.

    RBS has embarked on an audacious journey to change their way of working through the adoption of Agile and DevOps in their legacy mainframe applications.