Page: 1...... 5 6 7 8 9 10 11 12 13 14 15......38 <prev | next>
Lessons learned should be captured and placed in a database log that will be available to the project management team. Use in conjunction with the other templates in the Lessons Learned Package.
The main objective of a lessons learned session is identifying how to sustain strengths and improve weaknesses on future projects. These instructions help you determine when and how to conduct a session, and includes links to helpful forms to comprise a handy Lessons Learned Package.
What worked well on your project? What didn't? Document and share your lessons learned via knowledge areas like scope, cost, risk and communication using this Excel sheet. Use in conjunction with the Lessons Learned Charter/Facilitator Program Overview.
The aim of the template is to capture lessons learned consistently across an organization. Capturing key project-related data in a consistent manner helps other project teams (in a different location, function, department) filter through and identify relevant lessons. The template can be used as is and shared via a local shared drive or in the cloud; or the format can be leveraged to create a SharePoint list to facilitate collaboration. Adapt categories and values to suit your needs.
To help you create lessons learned that will not get stuffed in a folder never to see the light of day, use this simple Excel template in your organization. The template should be used across initiatives so you have a single source of the truth on lessons learned in one file versus having to hunt through multiple files. Use in conjunction with the article Capturing Lessons Learned That Actually Get Used.
This log helps you collate both the positive and negative experiences throughout the life cycle of any software development project. The main purpose of this template is to collect, share, learn and improve from the real-time experiences you encounter during the project.
Traditional, multi-page business cases often don’t work well. They contain too much subjective information, and the relevant details are lost in the “sales pitch.” This lightweight business case template is more in the spirit of a Lean Business Case than a traditional one, but is more likely to be accepted by leadership.
This document details the impact a proposed IT project or major service change will have on the current and planned infrastructure of an enterprise.
After calculating the resources required (with the help of company productivity norms and with the time available), this schedule will help project stakeholders have a clear idea about the current and future manpower requirements for any given construction project.
This simple register is used to document meeting outcomes and actions to be taken, and also documents the list of participants/stakeholders. It is part of communications management.
Page: 1...... 5 6 7 8 9 10 11 12 13 14 15......38 <prev | next>
|
Egotism is the anesthetic that dulls the pain of stupidity. - Frank Leahy |
