| Content Levels | |
| Register for free access to papers, case studies, and over 50 templates. | |
| Subscribe for complete access: $14.95 monthly or $149/year | |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Abstract
Legacy system migrations are one of the largest and most common software development projects organizations undertake. These projects are often considered to be too big or too unwieldy (or too critical) to use agile development methods. But many key agile practices can be even more important in migration projects.
What this is
This paper discusses several factors a team facing a legacy system migration needs to consider; and how proper application of agile methods and techniques can help them reduce risk and increase their chance of success. The author points out key considerations that most legacy system migration projects face, and suggests some ways to address those problems. Project preparation, the project team, release and iteration planning, and engineering practices are all addressed.
Why it's useful
When it comes down it, legacy system migration is just another software development project, but one that happens to have an additional source of information, requirements, and constraints that other projects dont—an existing system. By applying some of the suggestions in this paper you can make both current and future system replacement more successful.
©Copyright 2000-2012 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy