Curious Cat Management Improvement Blog: Deming, lean thinking, innovation, customer focus, continual improvement, six sigma.
April 11, 2007
Google Software Engineering

An interesting series of posts on Google NYC, Top Google engineer talks to NYC software industry:

Google NYC is not a specialized engineering operation, its 300 engineers work in teams of three on the full gamut of Google products and services. Currently, Google NYC engineers are working on about 100 different projects.

Of Google’s 8000 employees worldwide, approximately half are engineers. Warren stressed that Google pro-actively seeks to keep an engineering-centric culture and does all in its power to avoid undue influences from the likes of biz dev, VC and marketing folks.

Google continues to stress the importance of letting engineers pursue customer delight. It seems to be working pretty well, even if some don’t like the primacy of engineers at Google.

Google Engineering: The REAL story

The Google agile development process begins with “upfront ideation,” Rechis said, and “story creation” follows. Once “stories are in place,” a highly managed “weekly sprint” development cycle is set in motion, with multi-functional teams working to meet supervised deadlines. Development teams typically are comprised of a Project Manager, a User Experience Engineer and a Technology Lead prioritizing workflow. Project schedules are set and reviewed for compliance in regular and frequent team meetings:

Engineer finishes task, Produces build for User Experience approval, Engineer releases into build, Build QA’d. Build stage for release…

The Google “weekly sprint” methodology enables flexible iteration integrating user feedback during the development process, Rechis indicated. As is the Google rule, he concluded, “focus on the user and all else will follow.”

Related: Stretching Agile to fit CMMI Level 3 - Agile Management - Google New York Speaker Series

One Response to “Google Software Engineering”

  1. Curious Cat Management Improvement Blog » The Software Engineering Manager’s Lament Says:

    [...] agenda [quality, time or price], which two has to be resolved via a power play. In companies with a strong engineering culture, the engineers pick quality. It’s their professional pride on the line, after all. So they [...]

Leave a Reply



Curious Cat Management Improvement Blog © curiouscat.com 2005-2009 powered by WordPress

Internal Links

Author

John Hunter

Tags


Full tag could

Other

Search Blog

Web Search

Management Improvement web search

Recent Comments

  • Jaky Astik: Where there are no problems there is no leadership, because then, no one cares.
  • Tim McMahon: Your post and Shaun’s comments are quite right. I think the there is an evoluation in thinking as...
  • Richard Kunkle, MD: Great blog. What is intriguing here is that we as physicians have focused here on the needs of...
  • Josh: When I buy a car, I want to be able to drive the car to work/home which is about a 20 minute commute each way...
  • Alex: Wow, Google has done it again. This is truly going to change the dynamics of communication as we know it today....
  • Anonymous: We should all be grateful that Toyota is helping out the US economy. My cousin landed a job with Toyota...
  • Oscar: That’s pretty cool from one side but 4 hours to refill the tank is too much time i think. I’d...
  • shaun sayers: This is quite a significant issue Jon, and there is a fine balance to be found On the one hand I...

Archives

April 2007
M T W T F S S
« Mar   May »
 1
2345678
9101112131415
16171819202122
23242526272829
30