Posts
411
Comments
228
Trackbacks
42
The Hidden Cost of Scope Reduction

Scope reduction in a project is generally seen as a positive activity.  In small applications this is generally true.  This is not always the case though, especially in an enterprise environment.  The key determining factor is the down steam impact of removing the feature from scope. 

If the item has already been planned for by other project teams the rework could be more expensive then what is being saved.  Does eliminating the task mean that other applications need to plan for development or processes to cover the gap.  The requirement needs to be of an isolated nature such that the only effect is to that particular component.  At the least the impact needs to be understood and acknowledged by the stakeholders.

As with most decisions on a project you need to weigh the benefits and the costs.  Along with the collateral damage you should also consider the long term implications.  If not implementing something now means implementing it later at a higher cost you may want to reconsider.  Be a surgeon and not a lumber jack.  Only cut away what you have to.

posted on Friday, September 1, 2006 1:24 AM Print
Comments
No comments posted yet.

Post Comment

Title *
Name *
Email
Comment *  
 

Tim Murphy

Tim is a Solutions Architect for PSC Group, LLC. He has been an IT consultant since 1999 specializing in Microsoft technologies. Along with running the Chicago Information Technology Architects Group and speaking on Microsoft and architecture topics he was also contributing author on "The Definitive Guide to the Microsoft Enterprise Library".



I review for the O'Reilly Blogger Review Program



Technorati Profile

www.flickr.com
Tag Cloud