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.
Advisor
Scope Creep or Responding to Business Change
Posted November 24, 2005 | Leadership |
About The Author
Jim Highsmith is a Cutter Fellow Emeritus. He was the founding Director of Cutter’s Agile Product & Project Management practice and received the 2005 Stevens Award in recognition of his work in adaptive software development and Agile processes. Mr. Highsmith has 30-plus years’ experience as an IT manager, product manager, project manager, consultant, and software developer. He has consulted with IT and product development organizations and… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.