Linked by Thom Holwerda on Wed 20th Aug 2008 02:16 UTC
Last week we reported on the Engineering 7 weblog, a weblog headed by Microsoft's Steven Sinofsky on which they promised to chronicle the development process of Windows 7, while allowing us normal folk to give feedback. They are keeping their promise, as the latest post by Sinofsky offers some interesting insights into the various development teams working on Windows 7.
Permalink for comment 327408
To read all comments associated with this story, please click here.
Generally a team gets unwieldy past 15 or so devs, so if there are 25 product teams of 10-15 devs per team, that means there is 250 - 375 devs directly working on windows. The generally accepted ideal number of testers to devs nowadays is 2-1, so add in an easy 500 - 750 people for testing. So devs and testing alone, you are talking 750 - 1125 people working on windows, and that is not counting project managers, designers, localization teams and middle management.
The shop I work at has around 80 people, the place before was closer to 120, including sales guys. I can't even imagine working on a project with those kinds of infrastructure concerns.
Member since:
2006-02-05
Generally a team gets unwieldy past 15 or so devs, so if there are 25 product teams of 10-15 devs per team, that means there is 250 - 375 devs directly working on windows. The generally accepted ideal number of testers to devs nowadays is 2-1, so add in an easy 500 - 750 people for testing. So devs and testing alone, you are talking 750 - 1125 people working on windows, and that is not counting project managers, designers, localization teams and middle management.
The shop I work at has around 80 people, the place before was closer to 120, including sales guys. I can't even imagine working on a project with those kinds of infrastructure concerns.
Edited 2008-08-20 02:38 UTC