The Agile methodology has become increasingly prevalent in software development. We believe that techniques from this method of software development can be effectively put to use in
implementing software. In our experience, organizations that use a phased, iterative approach to implementing a complex system can see significant benefits. Organizations, like individuals, learn and mature over time. Recognizing that an organization (or individual) doesn’t know everything they possibly need to know on the front end of a project strengthens the argument for rapid iterations. Organizations can (and in many cases
should) change rapidly. Agile approaches a complex problem by breaking it down into many small parts that can be incrementally solved and brought back into a cohesive picture. This approach allows changes to be more easily incorporated. It is, of course, still important to hold the line on unnecessary changes during any project. However, in some cases, business fundamentals shift in front of your eyes and there is no sense in pursuing a set of requirements that no longer solve the current business problem.
While there are many benefits to a rapid and iterative model, some organizations must have a large initial phase to get a base system in place. We agree that it is necessary to do this in many instances where the legacy system being replaced has roots in multiple operational areas. However, even within that first large phase, the idea of rapid iterative sub-phases can be applied. For example, each functional area can be broken out as a sub-phase that has its own iteration cycle, repeatedly testing integration with the larger project at key milestones.
In our particular case, we are able to take advantage of the Aptify Application Lifecycle Platform to help with these concepts, but the idea is not product or technology specific. For more on Agile, take a look a
this Wikipedia article. Keep in mind that many of the concepts described in the article will have to be interpreted a bit differently in the context of implementation rather than development, but they largely apply.