requirements creep | can be avoided by - using incremental development
- carefully documenting the problem boundaries at an early stage
- estimating the time any proposed requirement will take
- . deferring major changes to subsequent releases if possible
| ![2001-08-30 14:57:18.0](facet.gif) |
has definition The tendency for the set of requirements to relentlessly increase in size during the course of development, resulting in a system that is more expensive and complex than originally intended | ![2001-08-30 14:57:18.0](facet.gif) |
is a subtopic of 4.9 - Managing Changing Requirements | ![2001-08-30 14:57:18.0](facet.gif) |
is a kind of process | ![2001-08-30 14:57:18.0](facet.gif) |
may result in very significant cost overruns in projects | ![2001-08-30 14:57:18.0](facet.gif) |
occurs when changes to a system are really enhancements in disguise | ![2001-08-30 14:57:18.0](facet.gif) |
process | see also process^2 | ![2001-08-30 14:57:05.0](facet.gif) |