Out of every 100 IT projects started, 94 will start over again at least once. Before your company launches its next package selection, implementation or upgrade, make sure you don’t cripple the project from the start by failing to identify your requirements – the number one reason that projects spin out of control. Make sure that your company has a clear understanding of how important the requirements definition stage is, has a proven way to carry it out properly, and doesn’t skip this critical phase in the rush to get an RFP out the door.

This white paper summarizes some of the key lessons we have learned through our industry-leading requirements definition practice.