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 and people recommend or prefer other methodologies like LeSS or SAFe. 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? State of Scrum Report 2015 says 33% of 5000 people responded have distributed teams and this number should have gone higher YOY. How can engineering practices be standardized across team for optimal throughput? 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? How does definition of done work for multiple teams?
Audience will be able to understand how Scrum can be used in large programs and deliver value to the customers. The session will also address and clarify the roles that can be scaled, its benefits and shortcomings if any. The audience will be able to comprehend various techniques that can help the Scrum Masters and Product Owners to manage the dependencies, solve communication barriers etc to maximize value delivery. The audience will be able to streamline the process of the definition of done which can help their teams to achieve maximum throughput.