InfoQ

News

Presentation: Agile Project Management: Lessons Learned at Google

Posted by Abel Avram on Jul 03, 2008 01:00 AM

Community
Agile
Topics
Adopting Agile
Tags
QCon ,
Scrum ,
Qcon London 2007

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum. He tells how Google started with no engineering management, then gradually introduced Scrum without spoiling the development culture formed over the years.

Google removed all low level engineering management back in 2001. They formed lots of small teams of 2-3 developers which constantly took the leadership of their team. They were responsible for what they were doing, including fixing bugs in production code without asking anyone about that. That created a special development culture in which everyone was feeling completely responsible for his contribution to the company and no one was expecting a boss to tell him what to do next. Later on, they started to gradually introduce Scrum step by step and forming organic management whose primary role was to support developers' activity and not supervise them. There are only two basic rules at Google: code reviews and every developer maintains a web page with information about his current work and his plans for the following 3 months.

The main problem Google was facing back in 2001 was missing the deadlines. As a reaction, they introduces backlogs and burn down charts. Then daily meetings. They were still missing dates. After a thorough investigations they discovered that a large number of features were work in progress. So, they started to minimize work in progress. Later they introduced iterations, and included testing tasks in the backlogs. Eventually they started creating release burn down charts.

The entire presentation is 1 hour and 8 minutes long. Jeff answers questions during the last 15 minutes of the presentation.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

1 comment

Watch Thread Reply

my feedback by Elham Moazzen Posted Jul 7, 2008 9:07 AM

  1. Back to top

    my feedback

    Jul 7, 2008 9:07 AM by Elham Moazzen

    I enjoyed it very much, thank you.

    Reply

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

  •  Jul 02, 2009,
  •  

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

  •  Jul 01, 2009,
  •  

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

  •  Jun 30, 2009,
  •  

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

  •  Jun 30, 2009,
  •  

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.