It's not that much different from a greenfield project. In fact, if done in an iterative way, every greenfield project basically becomes a maintenance project after the first iteration.
Why do you ask?
Moving to our Process forum...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Jul 04, 2004
I have had a question about the various phases involved in a maintenance project So i posted....
Can you summarize the phases...in order..
Thanks in advance Regards [ July 26, 2006: Message edited by: A Kumar ]
Joined: Jul 11, 2001
It would be much easier to help you if you provided more context:
- what do you already know about maintenance projects, - what other resources have you already tried (google?) and how did they not provide what you needed, - what will you do with the knowledge once you have it?
Joined: Jul 04, 2004
I havent worked previously on a maintenance project...probably the next one would be that
Did Googling..and searched the Wiki..There was useful info...
But thought that you guys can also give me some info..
I believe that the latter part of the SDLC remains the same whether for the a Development or a maintenance project..
but how about the intial...part where you may have analyse for the issues
The agile "planning game" would be a good exercise. Take a day or two in a big room with all the important players, list all the maintenance stories you can think of on index cards, get the the people who use the app and/or the people who pay for it to put the cards in order from most important to least. (I hate "high, medium, low, urgent, cosmetic" and all the other priority ratings. Just put them in order, 1..n.) Estimate each one the best you can, see how long they would all take.
That gives you a pretty good idea of what you should be working on and how long it might take.
BTW: You might introduce some tasks that the customer doesn't care about at all. Clean up the code repository, upgrade to a new release of UDB, whatever. A couple times over the years we have told our customer that for every $100 you give us, we will work $90 on your stories, but we have to work $10 on some under-the-covers technical stuff.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
If you're interested in a full SDLC, you might find the Enterprise Unified Process (EUP) to be revealing. As you can see, I add a Production and Retirement phase to the RUP lifecycle, as well as a few new disciplines. I think that a common mistake that people make is to talk about a "maintenance phase". What really happens, if you step back from the traditional mindset a bit, is that a system goes into production. While it is in production potential defects and new requirements are identified for it. Those potential changes are either addressed immediately as a "hot fix" or fed back into the development cycle for a future release of the system. In short, change management occurs during the production phase.