InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Google's Lean Software Process

Posted by Deborah Hartmann Preuss on Jul 10, 2006

Sections
Process & Practices,
Architecture & Design
Topics
Delivering Value ,
Stories & Case Studies ,
Agile
Tags
Continuous Improvement ,
Lean
Carlos E. Perez is an object-oriented practitioner and Artima blogger with an interest in process - right now, Google's software process.  From what he's found in public sources, including a paper presented to the Silicon Valley Product Management Association by Google Product Manager Marissa Mayer, he is impressed not only with what they are doing, but the scale on which they are doing it.

On the Manageability.org blog, Perez asked, "How closely do Google's development practices match Lean Software Development?"  By way of answer, he looked at each of the seven Lean Software practices, and how they are reflected in the Google process. 

The seven Lean Software Development practices, from the book by Mary and Tom Poppendieck, are
  1. Eliminate Waste,

  2. Amplify Learning,

  3. Empower the Team,

  4. Deliver as Fast as Possible,

  5. See the Whole,

  6. Build Integrity In,

  7. Decide as Late as Possible.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.