How to keep the requirements/specifications in a project up to date?
I know there are some processes that involves the documention part. But what if the client does not like documentions, and does not want to devote extra resources to on documentions?
Currently my project has this problem. Once the requirements/specifications are done, they can hardly updated. Change request are issued in the bug tacker as features. This does not cause many problems during an intration or a phase of the project, but we had much trouble in the following phases to track the orginal requirements when found a issue that is not clear about the requiremnts. (the project has been in development over 3 years in a team of 5 devs, and the has about 500k LOC)
I planned to use wiki to manage the documents and involve the whole team to update the documents. But there is still extra cost.
Everything you will do to maintain your documentation will be costly.
As code is already developped you can't even plan to include part of the documentation in the code itself to generate part of the documentation during the build...
I'm afraid there is not much you can do except Magic.
You, or whoever is the main contact with the customer, has to make it clear what the issues you are having that are directly linked back to not having up to date documents.
It is up to you to show that the time wasted in later phases by designers, devs, testers etc is much more costley then the overhead of keeping the documents up to date in the first place.
Whichever format you have requirements, you will have to now spend time reviewing and updating them so you can get them into a proper state. This is a hit you will have to take for not having done it in the past (for whatever reason). Explain the risk of not doing this (the problems you now have will get worse and worse, and will probably eventually lead to whole areas of functionality not being able to undergo change as nobody is sure what it is meant to be doing in the first place)
Then the overhead of keeping them up todate, while it is a more visible overhead then the problems of not doing it, should mean less time spent getting the functionality working to spec and released