Comments on: Requirements, Risks, UnOffical Projects, and Pricey SharePoint Consultants. http://mittechnical.com/BOSTON-SEO-WORDPRESS/requirements-risks-unoffical-projects-and-pricey-sharepoint-consultants/2007 Project Management, Systems Analysis, Semantic Web, SEO, and Whatever Else... Fri, 21 Nov 2008 05:30:23 +0000 http://wordpress.org/?v=2.6.2 By: Josh http://mittechnical.com/BOSTON-SEO-WORDPRESS/requirements-risks-unoffical-projects-and-pricey-sharepoint-consultants/2007#comment-136 Josh Mon, 06 Aug 2007 11:36:46 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/requirements-risks-unoffical-projects-and-pricey-sharepoint-consultants/2007#comment-136 Not only do they invite scope creep, but what tells you what to build? What your test cases will look like? What your budget will be? It is a mess. Thankfully, good people are on the case now. Not only do they invite scope creep, but what tells you what to build? What your test cases will look like? What your budget will be? It is a mess. Thankfully, good people are on the case now.

]]> By: Stephan Meyn http://mittechnical.com/BOSTON-SEO-WORDPRESS/requirements-risks-unoffical-projects-and-pricey-sharepoint-consultants/2007#comment-132 Stephan Meyn Mon, 06 Aug 2007 00:16:48 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/requirements-risks-unoffical-projects-and-pricey-sharepoint-consultants/2007#comment-132 I am starting to understand more of it. Being a methodologist myself I am a bit curious about that methodology. It doesn't seem that MOSS necessarily is an inappropriate technology, just that the overall project gives some strong red flags about inappropriate project management. One thing to add to the risk list: any decision that is taken begs the question wether it is taken too early. See my last blog post on this. Not having scope and SOW are major risks because they invite scope creep. Give the PMO some literature from people like Robert Glass and the like. I am starting to understand more of it. Being a methodologist myself I am a bit curious about that methodology.
It doesn’t seem that MOSS necessarily is an inappropriate technology, just that the overall project gives some strong red flags about inappropriate project management.
One thing to add to the risk list: any decision that is taken begs the question wether it is taken too early. See my last blog post on this.

Not having scope and SOW are major risks because they invite scope creep. Give the PMO some literature from people like Robert Glass and the like.

]]>