Do you know this that feeling of guilt that after phase of the extensive analysis, design, and implementation, you apply last minute changes or fixes without a trace in the documentation?
Team spent countless hours on documentation of requirements and the design, and just like that it becomes out of date and loses its value. And only because there was no time, budget, processes in place, or someone was just lazy.
Do you know that feeling that after a while of the release you have no idea how this system is supposed to work?
Well, the solution is quite simple, and yet so hard: keep your documentation up to date whenever system changes. Easier said than done.
Do you know this? There’s this table and you have no idea what it is for – who created it, for what purpose, where does the data come from and what it’s being used for. Can we use it for this report or should we simply drop it? If only we had who to ask about this...
Solution is simple – create a documentation repository, assign objects to people and functional areas, ask your team to provide even basic descriptions. And share this documentation.