http://blogs.msdn.com/b/nickmalik/archive/2005/08/11/450578.aspxThis is an interesting question in business IT. I just sat through a long meeting discussing requirements for a project that is under way. The project started without a detailed list of requirements written out. So, the business adds a requirementen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/nickmalik/archive/2005/08/11/450578.aspx#461659Wed, 07 Sep 2005 01:49:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:461659Ontario EmperorIf you're lucky, the customer won't want to upgrade or modify the system in the future. But you already know that...<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=461659" width="1" height="1">http://blogs.msdn.com/b/nickmalik/archive/2005/08/11/450578.aspx#450654Fri, 12 Aug 2005 05:24:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:450654Brendan GBeen there, done that. And, vowed never to allow it to happen again!<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=450654" width="1" height="1">http://blogs.msdn.com/b/nickmalik/archive/2005/08/11/450578.aspx#450595Fri, 12 Aug 2005 01:45:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:450595Joe Chung&quot;No requirements management process&quot; -- sounds like you'll be missing several layers of stomach lining after this project.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=450595" width="1" height="1">