Microsoft said that it will publicly reveal details and “in-depth technical information” about Windows 7 to developers attending its Professional Developers Conference (PDC) set to take place from October 26-29 and at the Windows Hardware Engineering Conference (WinHEC) scheduled for November 5-7.
Writing on the new Windows 7 blog, Steven Sinofsky and Jon DeVaan, senior engineering team leaders, pledged to document the pace of development and offer a peak at Windows 7 features in the works from time to time. “With this blog we’re opening up a two-way discussion about how we are making Windows 7,” the company wrote. “We strongly believe that success for Windows 7 includes an open and honest, and two-way, discussion about how we balance all of these interests and deliver software on the scale of Windows. We promise and will deliver such a dialog with this blog.”[…]
A feature team represents those that own a specific part of Windows 7—the code, features, quality, and overall development. The feature teams represent the locus of work and coordination across the team. This also provides a much more manageable size—feature teams fit in meeting spaces, can go to movies, and so on. On average a feature team is about 40 developers, but there are a variety of team sizes. There are two parts to a feature team: what the team works on and who makes up a team. […]
Windows 7’s feature teams sound a lot like parts of Windows with which you are familiar. Because of the platform elements of Windows we have many teams that have remained fairly constant over several releases, whereas some teams are brand new or represent relatively new areas composed of some new code and the code that formed the basis of the team. Some teams do lots of work for Server (such as the VM work) and some might have big deliverables outside of Windows 7 (such as Internet Explorer).