One of my goals for this year is to try to improve the documentation process within the R&D-department. My first step have been to sit down with each developer and talk about documentation in general and how they feel about our current documentation process.
The (almost) unanimous response I got was;
- I can't find the documentation I'm looking for.
- I don't trust the documentation I find as it is probably outdated because nobody updates documents once they are created.
- Process? Well we put whatever document we create in the documents folder and that folder is a mess...
- I miss information related to requirements, design and implementation.
- Creating documents can be hard. Document templates would help.
- It is very important that we document what we should do and what we have done!
This is terrible! Because this means that whatever documentation that is created is "worthless". The good thing is that I there is a common urge from the team to actually fix this.
We have a team building activity coming up in two weeks and my manager have given me a few hours for discussions around this topic. The question is - how would you spend these hours to make sure that you got the best result?
The background to this is that I a while back asked a question on how to resolve the problem of a non-existent pseudo process, How do I improve the development process when the only 'spec' is a "slogan" from management.
As a consequence I have started working more on involving the team around the problems that I see. And less of my just keep presenting solutions to problems they haven't really thought about.