How can we be sure we've identified all of the ramifications of a requirements change?

Establishing a project's requirements is almost never a one-time event (though projects would be simpler if it were). At some point, even well planned projects will have to respond to changing business needs, technology, solution options, and more. Requirements changes made without thorough consideration can wreck havoc by causing unanticipated changes in other requirements and in the solution design.

To avoid the chaos that can result from unexpected changes, it's important to establish, before change happens, how potential changes will be assessed, prioritized, and implemented.

Log in or Subscribe now to read the full answer...