Gatherspace.com vs. Jama Connect Comparison Chart

For a project manager or business systems analyst, it’s customary to meet with a project 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. To easily identify scope creep, you first need to have a really good handle on what the requirements are. Make sure you have an organized requirements management document that includes a mission statement, a background statement that includes needs, the high level features, and as many detailed requirements as possible which all map back up to the features. By producing a rich and thorough set of requirements, you can get a clean baseline of what the system needs to do which can often mitigate any upfront scope creep.