How to Deal with Out of Control Requirements and Save Your Project
by Darren J. Levy
For a project manager or business systems analyst, it's customary to meet with stakeholders to obtain project requirements signoff. However, what invariably happens is the customer deciding they need a new set of features outside the scope of the current requirements document. This dilemma, known as "scope creep" or “feature creep” is a common project killer, and it is critical for a project manager to know how to effectively manage this situation when it occurs.
| Attachment | Size |
|---|---|
| How to deal with Out of Control Requirements and save your project.pdf | 126.66 KB |
On-target by einarsen
re: great point about your question by kbryant
A teachable moment? by rtmerrill
Walkthroughs by dwright
Rules are not requirements by jamet123
Rules can be thought of as requirements by bcarkenord
Iterative and Incremental by kmatthews
Implementing requirements in priority order gives greater ROI by ScottWAmbler
