The RADXP process helps control scope. By the end of the design phase, the solution provider and the customer have good documentation of what needs to be built during the execution phase. This documentation helps prevent expanding scope, or mission creep, as it is sometimes called.

Projects that run twelve months or longer are never done. Before the project is half way done, the requirements have changed. Some solutions by their nature cannot be completely achieved in 90 days. The RADXP methodology forces the customer and the development team to focus on true priorities and do first things first. By analogy, look at the U.S. space program. The United States did not go directly to the moon. First, we launched a satellite, then a dog, then a man, then the man made a space walk, etc. A billing or logistics system should be no different. Even if one could launch everything at once, the users and the business processes could not handle it. A staggered implementation naturally takes into account the inherent problems of learning curves, transitional efforts, undetermined process definition and provides flexibility of design.