Being Agile with Legacy Applications

A common question is how to deal with legacy applications.  There is a lot of confusion on how to deal with legacy with most people confused on what to actually do.  They end up maintaining and patching the old code eventually to the point where a full rewrite is ordered and the cycle then repeats.

Then the rewrite proceeds to do a one for one replication of features in a new architecture but then degeneration starts again any after the new version  is released in one fell swoop after many months or years of development.  This also fails to take into account whether the legacy features are actually needed and therefore waste is introduced during the rebuild.

How about if you could enhance the legacy application by applying patterns that help remove the legacy code in a gradual and calculated manner.  Yes, it can be done and has been done.

Here are some sources of information you can look at:

There are other sources in the Agile space that help.  You many know of other sources directly related to the subject.

Please let me know if you know of anymore.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: