Software Process Model in MS

Lately, we guys had some casual discussion about the Software Process Model in MS.  It’s an interesting topic worth revisiting and writing down.
 
Most projects in MS follow Waterfall Lifecycle Model.  Why not RUP?  Unnecessary.  Why not Agile Methods?  Unnecessary.
 
Agile Methods provide:
  • 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?
Agile Methods require:
  • 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.

开张

这是我的第二个Space。前一个主要写生活,这一个主要写工作。我喜欢把工作和生活分开,Space也只好如此。
 
在写东西方面,我非常非常懒。这个Space开了许久,一直没有勇气开张。直到前两天,有一个朋友用“牛人一般都不写Space”讽刺我,让我终于迫不得已鼓起勇气……
 
我急切地需要锻炼英语写作,而我发现在写生活的时候,用英语恰如其分的表达情感是多么的痛苦。此处既然写工作,就尽量使用英语自虐好了。
 
谢谢。