Scope Creep or Responding to Business Change

by Jim Highsmith

The literature of software development and project management "problems" is rife with descriptions of the dreaded "scope creep." Projects take too long because customers are always changing their minds and developers find cool new features to add. However, there is a big difference between scope creep, which is a problem and to be avoided, and the necessity of responding to business changes and the evolving requirements.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Scope Creep or Responding to Business ChangeThu Nov 23 17:40:17 CST 2005