Organizations across the globe are embracing agility using different methodologies and frameworks to meet customer demands and improve time to market. Scrum is one of the most popular frameworks within which people can solve complex adaptive problems, while productively and creatively delivering products of highest possible value. Scrum was developed to work best within a team size of 5 to 10 members and has to be cross functional to be effective and efficient. It becomes easy for the Scrum team to achieve synergy and resonate with each other if the team is collocated further. The Product Owner, Scrum Master and Development team work in tandem with fewer problems to deal with however and can release most valuable features quickly. The challenges and impediments increases with the addition of every Scrum team. There is also a general myth that Scrum may not be suitable for large scale projects or programs.

Can Scrum be used for large programs (involving more than 5-6+ scrum teams) and still address top priorities like fulfilling customer needs, improving time to market and reducing cycle time? The answer is "YES"

Nevertheless, some of the questions that comes to our mind quickly when we think of scaling delivery using Scrum are below,

  • What challenges would arise when the team becomes distributed globally?
  • What happens when there is one product backlog that is shared by multiple teams and one product owner who is influencing all teams?
  • How does prioritization work for different teams?
  • How can Scrum Masters motivate and help the team to maintain the focus and deliver one product increment every sprint?
  • As there is One Product Backlog and One Product Increment, how do the Scrum Ceremonies like Sprint Planning, Backlog Grooming, Daily Scrum, Sprint Review & Sprint Retrospective happens with multiple teams and structure in place?

I plan to address the above questions (and few more) based on my experience with 2 large programs (using Scrum) I led in the past 5 years.


Outline/Structure of the Presentation

Presentation will be on the below agenda:

  • (5 mins) The Journey with Vision, Goals and Objectives
  • (8 mins) Challenges
  • (7 mins) Team and Product
  • (5 mins) Tools and Technical Practices
  • (5 mins) Continuous Improvement
  • (5 mins) Maturity Level
  • (5 mins) Key Learnings
  • (5 mins) Q&A

Learning Outcome

Understanding of scrum in large scale product development

Learn about how and when to scale product owner roles

Tips and Tricks on using SCRUM for large scale product development

Key challanges and mitigation while leading large programs

Learn about the technical best practices that can help accelerate development in large programs

Target Audience

Scrum Master, Agile Coaches, Product Owner, Project Managers, Program Managers

Prerequisites for Attendees

Exposure to Scrum Framework.

Exposure to Product Development using Scrum.


schedule Submitted 2 years ago

Public Feedback