While linking development to requirements is an intuitive notion, when put into practice, managing the complexities of changing project requirements can present significant challenges. Ineffective requirements management can create inconsistencies that remain undiscovered until the final phase of development, which is when the code is most difficult and most expensive to fix. In the “rush to code,” development teams often lose sight of the fact that mapping projects to requirements is the best way to guarantee project success–delivering code on time that meets customer expectation–with the ability to effectively manage the inevitable requirements changes customers request as the project moves forward.