In: Root » Business » Management
Purpose Work results are the output of any project effort. The documentation for work results is a record that the effort has been completed and the output has been produced. It is used as proof that the effort was put forth. As with technical documents, work results are used for a wide variety of purposes associated with the varied nature of the work that was completed. Application Documentation from work results is used as affirmation that work has been accomplished as prescribed. If work was completed in a way other than how it was originally specified, the work results documentation will reflect that variance. The documentation is used as a tool to build evidence that progress is being made, that deliverables are being produced, and that effort is being put forth. At the work package level, that information allows the project manager to build a piece-bypiece history of project progress. At the summary levels, that information can be presented to management or the customer to highlight the volume and nature of work accomplished. Content The work results documentation content will vary somewhat, based on the type of work that has been accomplished. The content should be structured consistently, however, to ensure ease of understanding and use. The documentation should include the original requirement, any coding or numbering for that requirement, the start and finish dates for the effort, the owner of the activity, contact information for the owner, and the status or dispensation of the final deliverable or output. Approaches The work results documentation may be attached directly to the work output itself. Thus, the documentation may serve as a cover page or introductory table for that information. Considerations There is a temptation on some “lesser” activities (including many administrative functions) to overlook or forego this type of documentation. That’s understandable, because it is an administrative effort in itself. However, it is precisely those types of activities that may be addressed most effectively by this type of data capture, since it may highlight work that was not required, variance that has not been addressed, or lesser levels of effort that have been overlooked or dropped. Conclusion During execution, project managers may become so overwhelmed with the volume of work and the level of activity that organizational practice can easily be forgotten. Thus, the forms and formats included herein often serve to preserve the process by virtue of their adherence to rote performance of basic reporting, tracking, and information storage tasks. The key is consistency. The more consistent project managers become in their management of communications and information, the more effective they are.
|
|||||||||||||
Disclaimer
1) E-articles is not responsible for the information contained by this article as well for any and all copyright infringements by authors and writers. E-articles is a free information resource. If you suspect this article for any copyright infringement, please read the terms of service and contact us or use the "Report this article" button on this page to investigate the problem.
2) E-articles is not responsible for inaccuracies, falsehoods, or any other types of misinformation this article may contain and will not be liable for any loss or damage suffered by a user through the user's reliance on the information gained here. |
|||||||||||||
