I recently wrote a non-traditional paper looking at how it might be possible to integrate Agile practices into a software maintenance activity. Academically I don’t expect the paper to go over so well – but, believe it might be of interest to some who’ve been asked the same questions as me.

The paper uses a very simple “helloworld” application written in Ruby and highlights a few really cool Ruby tools.

Anyway here’s the paper in PDF form – feedback always appreciated.

I’ve also written a very similar paper on the potential for IV&V integration into an Agile project. I’ll probably post this one as well in the near future.

1 Response Follows

  1. James Lorenzen says

    I loved the Scott Ambler definition of TDD. Unfortunately it’s been a long time since I read definitions like this and it’s refreshing to hear it again. I try my hardest preventing coworkers from putting more than “just enough production code” in when it is not necessary. It’s one of my biggest annoyances. Software maintenance is expensive enough without having to maintain code that supports no official customer requirement. “Oh but we might need that, or perhaps this a neat feature, or in 6 months we will have to do this.” 6 months later that feature is obsolete and we end up supporting it for 6 months.

    good job


Your Response