334 Part V: Closing Your Software Project Using (Web hosting faq)
334 Part V: Closing Your Software Project Using Teamwork When Writing Documentation The project was not a solo project; if it was, you couldn t really call yourself a manager. Because many hands worked on the project, many hands should also work on the documentation. Developers can write sections about development lessons learned, to be read by future developers, far better than you can. Your focus should be on the project manager s section, as well as rounding up the whole document to make sure it has as consistent a look and feel as possible. Some project managers add a technical writer to the team from the beginning with the purpose of them heading up the creation of a look-and-feel document (to direct the formatting and tone of written work from a corporate perspective) or style guide (to handle standards for spelling, grammar, and other particulars), as well as accompanying documentation for your project. In fact, many companies have set procedures for formatting and writing important documents. If your budget allows you to hire a technical writer, you ll find that this is money well spent. Here are a couple of important tips to keep in mind: Have meetings: When you finish the lessons learned document, the document should be something that everyone on the team is familiar and comfortable with. That does not mean they have to agree with all of it many times we would like to not see specific problems put in writing in the hopes that they will be more quickly forgotten but it does mean that you should hold meetings to discuss issues and work through them. Set milestones: Just as timelines exist for other parts of the project, they should exist for the documentation as well. You will find yourself needing to provide motivation to keep it moving along. Treat this part of the project as if it is as important as the creation of any module or component (it is as important!), and make sure that it gets done. You may meet resistance from your team when it comes to documenting lessons learned. Reluctance to create this documentation can often be a result of fear. A developer may wonder, If everyone else knows what I know, I won t be needed. When you encounter this belief, you need to confront it head on and assure the individual that this document can serve to illustrate to everyone just how much they do know and make them even more relevant and valuable not the reverse.
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.