Software Process Model in MS

• Satisfy customer early (continuous, frequent delivery of value).  – For ordinary users, does it really matter to get Windows Vista sooner or later?
• Welcome changing requirements, even late.  – This is the crucial point.  The products of MS are all GENERAL solutions/services/platforms, ie none is custom-built.  So, why is it necessary to subject to serveral customers’ requirements change?

• Customers and developers work together.  – Impossible to involve all customers.  Extremely hard to select representative visiting customers.

But things are changing, escpecially in the most dynamic product lines, eg Windows Live.  Products in these fields exceptionally need to "Satisfy customers early".

To me, the most attractive Pro of Agile Methods is: "working software over comprehensive documentation".

Last but not least, the MS Nighhtly Build Cycle is the heartbeat of the project.  There is a huge incentive not to break the build.