Lessons Learned - Revision history

Freddie: Added part about a simplified lessons learned session.

2021-11-17T13:01:57Z

Added part about a simplified lessons learned session.

Supercrumpet: /* Suggestions for Project Survey prompts */

2021-08-12T04:06:09Z

Suggestions for Project Survey prompts

Supercrumpet: /* Project Survey and Scope */

2021-08-12T04:05:35Z

Project Survey and Scope

Emilyanthony: /* Introduction */

2021-07-13T15:52:05Z

Introduction

Emilyanthony: /* How? */

2021-07-13T15:47:17Z

How?

Emilyanthony: /* Templates and Further Reading */

2021-07-13T15:46:43Z

Templates and Further Reading

Emilyanthony: /* Templates and Further Reading */

2021-07-13T15:46:12Z

Templates and Further Reading

Emilyanthony at 15:45, 13 July 2021

2021-07-13T15:45:23Z

Emilyanthony at 15:40, 13 July 2021

2021-07-13T15:40:57Z

Emilyanthony at 15:40, 13 July 2021

2021-07-13T15:40:39Z

@@ Line 75: / Line 75: @@
 # What skills did you need that were missing on this project?<span><span><span></span></span></span>
 <span>Take the answers to these prompts, reformat them using the process above, and shape a lessons learned document. <ref>Veriscope. (2012, February 22). ''How to Facilitate an Effective Lessons Learned Discussion | VeriScope''. VeriScope. <a href="http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio">http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio</a></ref></span>
 =Templates and Further Reading=

@@ Line 64: / Line 64: @@
 # <span><span><span>Were we surprised in a static event?</span></span></span>
 # Were the project goals attained?
-# What went well? Provide examples of successes that happened during or because of the project
+# What went well? Provide examples of successes that happened during or because of the project.
-# What didn’t go well? Discuss unintended outcomes that happened during or because of the project
+# What didn’t go well? Discuss unintended outcomes that happened during or because of the project.
 # What might have been better handled if done differently?
 # What recommendations would you give to others who might be involved in future projects of a similar type?

@@ Line 42: / Line 42: @@
 ===<span>Project Survey and Scope</span>===
 <span>The person who will be facilitating the lessons learned session should prepare in advance by taking feedback through a survey of the team. The project survey will help the participants to be better prepared to respond during the lessons learned session and will also give them the opportunity to provide input if they are unable to attend.</span>
 <span>The project survey should be organized by category. The use of categories will ensure key information is not missed and will later help to focus the discussion. These categories can also inform a standardization of titles, making it easier for a team member in the future to identify which lessons learned are relevant to their research. Standard categories for each project should be defined and additional categories specific to a project can be added. Suggested categories include:</span>
-# <span> project management</span>
+# <span>Project Management</span>
-# <span>resources</span>
+# <span>Resources</span>
-# <span>technical</span>
+# <span>Technical</span>
-# <span>communication</span>
+# <span>Communication</span>
-# <span>business processes</span>
+# <span>Business Processes</span>
-# <span>requirements</span>
+# <span>Requirements</span>
-# <span>design and build</span>
+# <span>Design and Build</span>
-# <span>testing</span>
+# <span>Testing</span>
-# <span>implementation</span>
+# <span>Implementation</span>
-# <span>external areas</span>
+# <span>External Areas</span>
 <span>These categories can be subdivided into more detailed categories. For example, project management can be divided into the process groups: initiating, planning, executing, monitoring and controlling and closing. Planning can then be further divided into project schedule, risk analysis, etc. A simple approach is to begin with a few categories such as project management, resources, technical and external areas and then add more categories as needed. The project survey should also include specific questions for each category. These responses will be used by the lessons learned facilitator to guide the discussion during the lessons learned session. Three key questions should be included as part of the survey: 1) what went right, 2) what went wrong and 3) what needs to be improved.<ref>Mackay, J. (2020, January 29).''What to Do When a Project Fails: How to Document and Share Lessons Learned''. Planio.<span></span></span></span></span>https://plan.io/blog/lessons-learned-from-failed-projects/ </ref></span>
 <span>A team may benefit by limiting the scope of the lessons learned meeting. Make clear in the planning for the meeting the scope of the lessons to be documented. For example, at a design deadline, only capture lessons learned relevant to the design phase of the project.</span>
 ===<span><span><span>Suggestions for Project Survey prompts</span></span></span>===

@@ Line 1: / Line 1: @@
 [[Category:Project Management]]
 =Introduction=
-Lessons learned is a project management documentation tool used across the lifecycle of a project to capture risk-causing events such as items which impacted the schedule, component failures, and oversights by the team or the project manager.<span></span>Lessons learned can also document items which went well, especially those which were unexpectedly positive, such as a new system integration that improved lap times, valuable feedback from design judges, or a networking opportunity with a sponsor.<span>They are<span></span></span><span>experiences distilled from past activities that should be actively taken into account in future actions and behaviors.</span>
+Lessons learned is a project management documentation tool used across the lifecycle of a project to capture risk-causing events such as items which impacted the schedule, component failures, and oversights by the team or the project manager. Lessons learned can also document items which went well, especially those which were unexpectedly positive, such as a new system integration that improved lap times, valuable feedback from design judges, or a networking opportunity with a sponsor. They are experiences distilled from past activities that should be actively taken into account in future actions and behaviors.
@@ Line 8: / Line 8: @@
 Many Formula teams are successful in executing only parts of the lessons learned process, illustrating a need to document the process in order to improve outcomes.
 =Where and When?=
 ==Sources of Lessons Learned==

@@ Line 24: / Line 24: @@
 =How?=
 Lessons learned are generated from a simple process:
 [[File:P2 01.jpg|link=https://www.pmi.org/kasimage/3ebfb6f9-3bb7-4d0e-a3f5-eebab14988d3/p2_01.jpg|alt=Lessons Learned Process|right|middle|frame|Lessons Learned Process]]
 ===Identify===
@@ Line 76: / Line 74: @@
 # What skills did you need that were missing on this project?<span><span><span></span></span></span>
 <span>Take the answers to these prompts, reformat them using the process above, and shape a lessons learned document. <ref>Veriscope. (2012, February 22). ''How to Facilitate an Effective Lessons Learned Discussion | VeriScope''. VeriScope. <a href="http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio">http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio</a></ref></span>
 =Templates and Further Reading=

← Older revision		Revision as of 15:46, 13 July 2021
Line 85:		Line 85:
	# https://www.girlsguidetopm.com/lessons-learned-in-project-management/		# https://www.girlsguidetopm.com/lessons-learned-in-project-management/
	# https://www.projectmanagementqualification.com/blog/2019/08/21/lessons-learned/		# https://www.projectmanagementqualification.com/blog/2019/08/21/lessons-learned/
		+
		+	=References=

@@ Line 81: / Line 81: @@
 =Templates and Further Reading=
-# <a href="https://www.smartsheet.com/content/lessons-learned-template">https://www.smartsheet.com/content/lessons-learned-template</a>
+# https://www.smartsheet.com/content/lessons-learned-template
-# Download warning:<a href="https://www2a.cdc.gov/cdcup/library/templates/CDC_UP_Lessons_Learned_Log_Template.xls">https://www2a.cdc.gov/cdcup/library/templates/CDC_UP_Lessons_Learned_Log_Template.xls</a>
+# Download warning: https://www2a.cdc.gov/cdcup/library/templates/CDC_UP_Lessons_Learned_Log_Template.xls
-# <a href="https://www.girlsguidetopm.com/lessons-learned-in-project-management/">https://www.girlsguidetopm.com/lessons-learned-in-project-management/</a>
+# https://www.girlsguidetopm.com/lessons-learned-in-project-management/
-# <a href="https://www.projectmanagementqualification.com/blog/2019/08/21/lessons-learned/">https://www.projectmanagementqualification.com/blog/2019/08/21/lessons-learned/</a>
+# https://www.projectmanagementqualification.com/blog/2019/08/21/lessons-learned/

@@ Line 1: / Line 1: @@
 [[Category:Project Management]]
 =Introduction=
 Lessons learned is a project management documentation tool used across the lifecycle of a project to capture risk-causing events such as items which impacted the schedule, component failures, and oversights by the team or the project manager.<span></span>Lessons learned can also document items which went well, especially those which were unexpectedly positive, such as a new system integration that improved lap times, valuable feedback from design judges, or a networking opportunity with a sponsor.<span>They are<span></span></span><span>experiences distilled from past activities that should be actively taken into account in future actions and behaviors.</span>
@@ Line 19: / Line 17: @@
 # Third party sources, such as other teams or sponsors
 It's important for a team member to recognize when information is valuable to be documented as a lesson learned versus in some other way, such as in design documentation or otherwise. From a project management perspective, lessons learned should focus on items which impact cost, schedule, or resources (facility, personnel, sponsorship, etc.).
 ==When to document==
 Lessons learned are also sourced from various parts of the project management cycle. Many formula teams overlook this, and only generate lessons learned after returning from the competition. Lessons learned should be identified as soon as possible. One approach a team may take is to generate each lessons learned from every team meeting, every month, or every critical milestone. Lessons learned should be ''identified'' immediately, but ''documentation'' and ''closure'' of the lesson should be done on a regular, scheduled basis. This ensures time has been taken to collect data and solve the actual issue, if present, before documenting it.
@@ Line 25: / Line 24: @@
 =How?=
 Lessons learned are generated from a simple process:
-−
 ===Identify===
 Identify the issue, comment, recommendation, feedback with a clear title.
 ===Document===
 Details of the event with as much information as possible. Include data, photos, emails, and other relevant information necessary to communicate the event.
 ===Analyze===
 Evaluate documentation and identify a solution or way forward.
 ===Store===
 In a repository or central location for the team to access later.
 ===Receive===
 Follow up on the lesson at the beginning of relevant phases of the project. '''This is the step most frequently missed by student teams and by far the most important.'''<span><ref></span><span>Rowe, S. F. (2008). Applying lessons learned. Paper presented at PMI® Global Congress 2008—EMEA, St. Julian's, Malta. Newtown Square, PA: Project Management Institute.</ref></span>
 ==Lessons Learned Session==
 <span>A lessons learned session focuses on identifying project success and project failures, and includes recommendations to improve future performance on projects. Project managers have an obligation to conduct lessons learned sessions for all projects with both their teammates and the external stakeholders such as the university, sponsors, and families who support the program, especially if the project yielded less than desirable results. The lessons learned session is a very important part of the lessons learned process. If the session is not successful, the organization suffers.</span>
@@ Line 61: / Line 57: @@
 # <span>external areas</span>
 <span>These categories can be subdivided into more detailed categories. For example, project management can be divided into the process groups: initiating, planning, executing, monitoring and controlling and closing. Planning can then be further divided into project schedule, risk analysis, etc. A simple approach is to begin with a few categories such as project management, resources, technical and external areas and then add more categories as needed. The project survey should also include specific questions for each category. These responses will be used by the lessons learned facilitator to guide the discussion during the lessons learned session. Three key questions should be included as part of the survey: 1) what went right, 2) what went wrong and 3) what needs to be improved.<ref>Mackay, J. (2020, January 29).''What to Do When a Project Fails: How to Document and Share Lessons Learned''. Planio.<span></span></span></span></span>https://plan.io/blog/lessons-learned-from-failed-projects/ </ref></span>
 <span>A team may benefit by limiting the scope of the lessons learned meeting. Make clear in the planning for the meeting the scope of the lessons to be documented. For example, at a design deadline, only capture lessons learned relevant to the design phase of the project.</span>
@@ Line 81: / Line 76: @@
 # What skills did you need that were missing on this project?<span><span><span></span></span></span>
 <span>Take the answers to these prompts, reformat them using the process above, and shape a lessons learned document. <ref>Veriscope. (2012, February 22). ''How to Facilitate an Effective Lessons Learned Discussion | VeriScope''. VeriScope. <a href="http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio">http://www.veriscopepm.com/2012/02/19/how-to-facilitate-an-effective-lessons-learned-discussio</a></ref></span>

← Older revision		Revision as of 15:40, 13 July 2021
Line 1:		Line 1:
−	[[Category:Project Management]]=Introduction=	+	[[Category:Project Management]]
		+
		+	=Introduction=
		+
	Lessons learned is a project management documentation tool used across the lifecycle of a project to capture risk-causing events such as items which impacted the schedule, component failures, and oversights by the team or the project manager.<span></span>Lessons learned can also document items which went well, especially those which were unexpectedly positive, such as a new system integration that improved lap times, valuable feedback from design judges, or a networking opportunity with a sponsor.<span>They are<span></span></span><span>experiences distilled from past activities that should be actively taken into account in future actions and behaviors.</span>		Lessons learned is a project management documentation tool used across the lifecycle of a project to capture risk-causing events such as items which impacted the schedule, component failures, and oversights by the team or the project manager.<span></span>Lessons learned can also document items which went well, especially those which were unexpectedly positive, such as a new system integration that improved lap times, valuable feedback from design judges, or a networking opportunity with a sponsor.<span>They are<span></span></span><span>experiences distilled from past activities that should be actively taken into account in future actions and behaviors.</span>