Introducing Agile to a legacy project

posted Thursday, April 07, 2005 9:19 AM
Brian Marick recently posted his “talking points” for how to introduce Agile to a legacy project.  I think this is something that is often overlooked in the agile community.  There is oodles and oodles of documentation about how to run an agile project when you’re starting fresh, but I haven’t seen very much on how to introduce agile into an existing “legacy” project.  Usually the team is deciding to give agile a try because of disappointments on previous projects, which are usually still around.  This poses some difficult problems since the legacy code usually doesn’t have very many (if any) tests, is likely highly coupled, and possibly a complete mess.  Brian’s post provides some good guidance on how to get started when you’re in such an environment.  The most important thing to note is that it should be gradual process, you can’t make a project agile in a day or week, but you can begin to see immediate benefits from moving in an agile direction.
0 Comments

Post a Comment

 
 
Prove you're not a spammer: 
9 + 8 =