Web hosting contract - Chapter 17: Documenting Your Software Project 335 Three
Chapter 17: Documenting Your Software Project 335 Three factors to consider when you write Whenever you write anything, whether it s operation of a site, you need to document lessons learned documentation, training mate-exactly what was done. Needless to say, rials, or system test plans, there are always you should also only make one major change three factors that you should take into account: at a time to fully realize the ramifications of that change before making any others. The method of documentation (printed or electronic): If it is electronic, can the docu- The target audience: Is the document to be ment exist within another document, or used to jog your memory six months from must it be a stand-alone document? If it is now, or is it something to distribute to all printed, is it a subset of a large document or users? If it is only for you, you can get by a stand-alone entity? with a few lines of terse notes. If it is for distribution to users, you need to be specific The scope of the documentation: Should and offer as much background information the document only address a change that as necessary without going overboard. was made, or should it be all-inclusive? Any time you make a major change to the Completing the Lessons Learned Documentation The input to any project should be the lessons learned document from previous projects. The output from any project should be the lessons learned document for future projects. In other words, you use previous lessons learned documents when you start your project. When your project is complete, you should be able to produce a lessons learned document as one of your deliverables. You should always start your lessons learned document at the beginning of your project to ensure you capture lessons learned right from the start. See Chapter 2 for information about initiating, planning, and beginning a project. Arguably, the lessons learned document can become the single most important document that a software project manager is ever involved in. It is your chance to pass on information to other project managers and to maintain records for yourself. Lessons learned can save untold time and money. Maintaining the lessons learned documentation throughout the entire project helps to keep things in perspective; you can show your software project team that it s acceptable to make mistakes (everyone does it) as long as you learn from mistakes and use the knowledge you gained to make better project decisions in the future. You can empower your staff to take calculated risks if they know that all mistakes offer opportunities to learn.
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.