Scaling Scrum & Distributed Teams – Scrum Tuning: Lessons Learned at Google

A fantastic Google Tech Talk by Jeff Sutherland, one of the founders of Scrum, where he introduces Scrum, Agile and offers a lot of insight and guidance on how to scale Scrume.g. the Meta Scrum.

Google Tech Talks
December 7, 2006

ABSTRACT

Adwords introduced a Scrum implementation at Google in small steps with remarkable success. As presented at the Agile 2006 conference this exemplifies a great way to start up Scrum teams. The inventor and Co-Creator of Scrum will use this approach in building the Google Scrum implementation to describe some of the subtle aspects of Scrum along with suggested next steps that can help in distributing and scaling Scrum in a “Googly way”. Credits: Speaker:Jeff Sutherland

Jeff discusses the following points:

• History of Scrum
• Introduction to the Agile Principles
• Overview of the ‘Toyota way’
• Fujio Cho (Chairman of the Board of Toyota) interview
• Overview of the ‘Google Way’
• Distributed Teams and Google Adwords
• Scaling Organisational Social Structure (Organic, Autocracy, Leadership, Bureaucracy)
• Scrum is ‘linearly scalable’ – double the team size, double the output
• Introduction to the Product Owner
• Introduction to the ‘Meta Scrum’ – (Chief Product Owner, Stakeholders, CEO etc)
• The ‘Meta Scrum’ at Patient Keeper
• Scaling Scrum
• The Scrum Framework
• What does ‘Done’ mean at your company?
• Introduction to Scrum Documentation, Meetings and Roles
• Introduction to the Scrum Master
• Introduction to the Release Burndown Chart
• Introduction to the Scrum of Scrums
• Work In Progress is bad!
• Introduction to XP ‘Spikes’ (timeboxed R&D)
• Fitting your Testing into your sprint!
• Nokia Scrum Assessment
• Changing the scope of ‘Done’
• Introducing the Sprint Backlog
• The Daily Scrum Taskboard
• The Wisdom of Lao Tse
• Hyperproductivity in Scaling Scrums
• Isolated Scrums, Distributed Scrums and Totally Integrated Scrums
• Case study on scaling scrum – distributed teams
• Project Reporting (Scope Additions, Burn Down, Cumulative tasks in QA, Work Closed Burn Up)
• Multi-threading and implementing a ‘Type C’ Scrum – when the same team is working on multiple projects