Comments for Coping with Project Scope; Eight Real-World Strategies at http://www.projecttimes.com , comment 1 to 1 out of 1 comments http://www.projecttimes.com Sat, 31 Jul 2010 02:36:06 +0100 FeedCreator 1.7.3 http://www.projecttimes.com/scope-management/coping-with-project-scope-eight-real-world-strategies.html#comment-348 Some good ideas but missing the two key aspects of scope which most prevent creep. First, scope cannot help but creep when it is defined in the typical manner as objectives, because nobody actually knows what they’ll get. Scope creeps much less when defined more appropriately as top-level REAL business requirements deliverable _whats_ that provide value when delivered by the product/system/software _how_. It’s the _awareness_ of the REAL business requirements that mainly changes, not the requirements themselves. Second, there are two different scopes; and much of creep occurs because of confusing them. The scope of the requirements is determined by what is needed to provide REAL value and is not a function of available time and resources. In my book, Discovering REAL Business Requirements for Software Project Success, related seminars, and requirements and REAL ROI™ consulting, I describe how to use the powerful Problem Pyramid™ to define the requirements scope so it doesn’t creep so much and becomes a reliable basis for negotiating the scope of implementation projects which the organization is willing and able to undertake. - RobinGoldsmith Sun, 15 Nov 2009 03:51:07 +0100