Talk:Lessons learned

Revision as of 18:34, 11 February 2023

In general, the content and figures in the original article are good. My focus is not going to be on rewriting what is already there, as the majority is well written and relevant. However, my focus is going to be on creating a better structure and a common red thread between the sections. In addition, I will be adding a number of sections and figures that will touch on things that are not already there. If you have any comments for what I have suggested below, please write your comments in the end of this page or send an email to s193974@student.dtu.dk.

My proposal for the structure of the updated article is listed below.

• Abstract
• Introduction
  • Setting
• Application
  • Methodology
    • Phase 1: Identify
    • Phase 2: Document
    • Phase 3: Analyse
    • Phase 4: Store
    • Phase 5: Retrieve
• Avoid project failure with the use of lessons learned
• Benefits and limitations
  • Benefits
  • Limitations
• Alternative approach to lessons learned
• Annotated bibliography
• References

Below I have described the improvements and changes I want to make. This list might be updated as I gain more knowledge about the topic.

General improvements

• Change the overall structure of the article to make it easier to follow and create a better connection between the sections.
• Create a red thread between the existing figures and tables and the ones I develop.
• Develop missing figures.
• Refer to all figures and tables in the text.
• Enhance the quality of the article by adding more references.
• Update the annotated bibliography and references.
• Add authors of the article.

Abstract

• Include the perspective the tool covers (uncertainty, learning: how can we know?).
• Include the project manager's role in using the tool.
• Rewrite the last past of the section.
• Update Figure 1.

Overview

• Remove the overview title and make the introduction the main title.
• Include the “big idea” - what is the purpose of the tool?
• Create less focus on the PRINCE2.
• Merge the introduction so it both contains the theory of PRINCE2 from the original article and merge it with the setting section.
• Develop a golden circle figure to support the content about the setting (why? how? what?).
• Update Figure 2.

Application

• Add an introduction to the application section before continuing to the methodology.
• Develop a figure which illustrates the lessons learned process in the methodology.
• Divide the methodology into five subsections, each describing a phase of the lessons learned process.
• Change the names of the lessons learned phases to the most commonly used in literature.
• Eventually change the methodology title to lessons learned process.
• Move the last past of the methodology down to the section about benefits and limitations.
• Move the setting section to the introduction.
• Rewrite the collecting and validating lessons learned section and implement it in the methodology.
• Explain how to collect lessons learned (i.e. a list of questions to ask during a lessons learned workshop).
• Update Figure 3 and 4.
• Update the table and give it a name.

Ensuring sharing the lessons learned

• Rewrite the section and implement it in the methodology. Add more content about storing lessons learned (i.e. PRINCE2 lessons learned log).
• Update Figure 5.

Write a section about how to avoid project failure with the use of lessons learned

Benefits and limitations

• Elaborate more on the benefits and limitations (especially the benefits). Currently this section is very short.
• Support the content with references. At present, the section does not contain any references.
• Remove the bullet points from the subtitles.
• Update Figure 6.

Alternative approach to lessons learned

• Compare lessons learned and the alternative approach more - what are the benefits and limitations of the alternative tool?
• Update Figure 7.

Annotated bibliography

• Update with new references.

References

• Update with new references.