The developer should not even know such processes exist. They should be baked into the tools.

To me, there are a couple of unique things we bring to the table. If you think about process, it's a dirty word for developers. But the development team manager says, 'We need to have a process'.

Windows Vista and the next version of Office will usher in a new user experience that developers can build upon and illustrate the capabilities of the underlying platform.

Historically, we focused on the independent developer. We wanted to make such developers highly productive. Visual Studio 2005 is no different.

But the processes out there, I think, are too heavy weight.