How the IE team is organized


The information published in this post is now out-of-date.

—IEBlog Editor, 20 August 2012

As we’ve been posting we’ve been mentioning our titles, but we haven’t really explained what those titles mean or what we do on the IE team, so I thought I’d explain.

Like many Microsoft product teams, there are three primary job functions that are dedicated to IE: Development, Test, and Program Management. In addition to these roles, we have key members of our virtual team who are shared with other parts of the Windows organization; these are jobs like SDK Writer, Localizer, Designer, Product Manager (a.k.a. Marketing), and Usability Specialist. These are critical roles for us, but I won’t spend a lot of time here describing those roles.

The IE team is lead by Dean Hachamovitch, our Product Unit Manager. He is the “CEO” of the IE team and has overall responsibility for all things IE. Specifically, we’re responsible for current issues with IE (e.g. security or hotfix requests) as well as the future of IE worldwide.

The rest of the team is organized by job function, with each of the functional managers reporting to Dean.

The Development team does the architectural design and actual programming for IE. This group is lead by a team of development managers and architects, one of whom you’ve met on this blog so far, John Bedworth.
 
The Test team is responsible for defining and measuring the quality of the product. They are lead by our Test Manager, Scott Stearns.

The Program Managers are lead by our Group Program Manager, Tony Chor (that’s me.) We have two primary responsibilities. First we drive the feature design of the product (understanding what our customers are doing and what they want, translating that information into features, determining what the UI looks like, etc.) Second, we manage the process of developing and releasing product (managing schedules, dependencies, tradeoffs, communication, etc.) Since many of you know Dave Massy, I’ll note that Dave is part of this Program Management team.

The leadership team (Dean and his direct reports) is responsible for defining the strategy and priorities for IE, allocating people and time to the various projects we have, and ensuring our work meshes with broader initiatives like Windows XP SP2.

Across the functional roles, we have feature teams that include the developer, tester, and program manager plus design, marketing, usability, etc. The scope of a feature team might be an end user feature like popup blocking or a broad initiative like performance or globalization. The real work of defining, developing, and shipping individual features happens at this level.

Given the complexity of what we do across our diverse user bases, the huge number of sites and applications we interact with, and the truly global nature of IE, we feel this organization allows us to both coordinate our efforts across IE as well as provide the in-depth attention each area demands. It also allows us to best grow the skills of our team members.

I hope this helps provide some insight into our team and some context for the posts and comments we’re making.

Thanks.
 Tony

Comments (11)

  1. Anonymous says:

    How many people are working on IE at any one time?

  2. Anonymous says:

    offtopic

    I see all of these posts about security issues — which are great insight for us… but will there ever be any posts regarding web standards and their support for CSS? The comments are filled with them, I have posted some as well… but will we ever tackle this issue or discuss if Microsoft is going to go this route? I would like to see a full post on your opinions of how this fits into the IE development — I know the fact that this whole blog doesn’t validate says a little already, but I’d like to hear atleast something if there’s a direction.

  3. Anonymous says:

    Hi Brady,

    We’ve certainly heard the feedback in this area. As it has already been discussed on channel 9 http://channel9.msdn.com we have not specifically posted on the topic here yet. It is currently too early in the project to make any promises about what we may be able to do when. However we are hoping to address issues effecting web developers as we plan for the future.

    Thanks

    -Dave Massy

    Program Management team

    Internet Explorer

  4. Anonymous says:

    I can understand that from a development angle — thanks Dave for the response, I look forward to reading more of this blog as it grows.

  5. Anonymous says:

    Hi Dave,

    Great write-up. Are you able to give us some numbers?

    Size of the IE team? Number in Dev, PM, Test?

    Thanks

    – Chris

  6. Anonymous says:

    Hey guys, I was just wondering what your developers "DEVELOP" in? I’m assuming VB, but I am interested none-the-less!

  7. Anonymous says:

    Oh yeah, and also how many developers you have working on this little puppy?

  8. Over on the IE blog , Group Program Manager Tony Chor describes the organizational structure of the Internet Explorer team. Although every product group at Microsoft has its own organizational nuances, the basic structure of most teams consists of a Product