Scaling Scrum To Large Distributed Teams and its Challenges

As designed for use, Scrum works well for small co-located teams, cross functional teams. As the popularity of Scrum starting growing, more and more companies started adopting Scrum with mixed results. But overall, the trend has been increasing. Off late, big enterprises have also started adopting agile for their business needs and building complex products. In a recent study, the number of enterprise customers adopting scrum has doubled in last 2 years and they have used distributed scrum on large programs. So, the question is, can agile scale beyond small and co-located teams and what challenges could be there?

This presentation talks about our experience of implementing scrum on a large program, the challenges of scaling scrum and how to overcome these challenges.


Outline/Structure of the Experience Report

1. Scrum the way it is designed

2. Survey reports on enterprise scrum adoption

3. Key consideration for large scale deployment

4. Challenges for scaling scrum

5. Approach to handle these challenges

6. Summary and Conclusion


Learning Outcome

The audience will experience:

1. Challenges of adopting scrum on large scale programs,

2. How to tailor some of the scrum practices

3. What is the goverance model

4. And do's and dont's based on our experience


Target Audience

Scrum masters, project and program managers

schedule Submitted 6 years ago

Public Feedback

    • Sachin Natu

      Sachin Natu / Naresh Jain - Inverting Test Pyramid - A First Hand Experience Report

      45 Mins
      Experience Report

      Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.

      Business Impact:

        Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.

        Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.

        Reduced test execution time - Backend tests are much faster. Almost 7-10  times faster than UI Tests - improved build certification time.

        Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.

    • Naveen Indusekhar

      Naveen Indusekhar - Research paper on 'What happens to Engineering Manager in Agile world'

      20 Mins
      Case Study

      This is an extremly simple topic with a very complex answer. I have spent last 3 years experimenting and working with lot of people to understand what happens to the so called Manager role in Agile world. With a self organizing, empowered team, does Manager still have a role? Do you shelve these senior people who drove all your deliverables in the past for your company? Do you just let go the technical expertize these people bring along?

      The research information around the experiment and results will be shared and am very positive that this will help lot of organizations move forward with great benefits. We will see how certain gaps that are created with introduction of Agile can be solved through these senior professionals. At the same time teams don't need to compromize or business doesn't need to compromize on new found agility by adopting any of the Agile practices.

      The very next discussion that I will touch base as part of this presentation is the role of Project Leads. Many Leads resist movement to Agile because they feel their growth will now be stagnated. Is this true? It is again an interesting data set captured by talking to Leads in waterfall world and understanding what they really aspire for.

      Looking forward to sharing my insights with real implementation and resulting data that I'm sure each of you will benefit from.

    • Naveen Indusekhar

      Naveen Indusekhar - 9 Steps to Agile Adoption: a fail-safe experiment

      45 Mins
      Experience Report

      While Agile adoption and practice is a complex model for mid/large sized Product companies to implement, we see a need for some sort of framework that can help drive it.

      Why do you need to be Agile? Where do you start, when do you start, and also how do you start? These are questions that reside in most of us during early stages of adoption. Here is a 9-Step breakdown that will help companies and teams adopt multiple Agile methodologies in different situations and scenarios. Maturing it from a ‘Persona Perspective’ framework helps the ‘decision-maker’ have a case for investment, further evaluate if it works, and improve it all through!!

      The discussion and idea is just my proposal that should help a team or an organization and is need not be the only way to implement Agile in an organization. Further detailing into these phases can form an overall Mindmap structure that is open to adopting from an organization and people standpoint.

    • Pooja Wandile

      Pooja Wandile - The ADAPT framework for agile transformation

      Pooja Wandile
      Pooja Wandile
      schedule 6 years ago
      Sold Out!
      45 Mins

      Innovation and faster turnaround of ideas from concept to realization is one of the primary drivers for organizations to stay competative in the market. Risk reduction, cost optimization, faster time to market, managing changing business priorities, focusing on delivering high business value are some of the key considerations for organizations when transitioning to agile. The transition journey will not be very smooth. It needs continous inspection while taking informed decisions as this change can have long term implications on several fronts within the organization. The change could be delicate and hence a well thought approach backed by strong senior management support is very crucial to the success of this journey. Here we propose a 5 stage framework for agile transformation called as ADAPT which also gels very well with the adapt philosophy of agile. The ADAPT acronym stands for Assess, Define, Adopt, Perform and Transform. Each stage is linked to some benefits that that can be derived from that stage.