D8

kouame
  • 6 months ago
  • 32
files (2)

Instruction.docx

This week, you are required to produce your Final Course Project Report. You will consolidate all project deliverables produced in prior weeks into your Final Course Project Report.

You will add one additional section for Lessons Learned. In this section, you will describe the strengths and areas of improvement within your project. The intent of the lessons learned is to serve as a repository for future projects as a function of continuous improvements. Upload a single ZIP/compressed file that includes all of your files together.

The Lessons Learned must contain the following sections.

· Introduction

· Lessons Learned Approach

· Lessons Learned Table

Use the Lessons Learned Tool to produce this project deliverable.

Grading Rubric

Category

Points

Procurement Management Plan

5

Procurement Strategy

5

Request for Proposal

5

Source Selection Criteria

5

Lessons Learned Introduction

30

Lessons Learned Approach

30

Lessons Learned Table

20

Total

100

Work on this project and then I will compress the files myself.

Lessons_Learned_Template_with_Instructions.docx

[Insert Department/Project Logo] [Insert Department Name]

[Insert Project Name]

University of Prosperity

Lessons Learned

Tool

University of Prosperity PPM Selection Project

PPM Selection Project

University of Prosperity

Lessons Learned | Page 9

Table of Contents

1 Introduction 4

2 Lessons Learned Approach 4

3 Lessons Learned Table 5

Introduction to the Lessons Learned Tool

The Lessons Learned deliverable serves as a continuous improvement mechanism in which successes and mistakes are documented. Lessons Leaned are fundamental for organizations and their journey to improve future performance. Furthermore, formally identifies, acknowledges, analyzes, and documents the lessons learned. Finally, collecting lessons learned over time adds to the organization’s body of knowledge related to project management and provides a rich source of information for current and future work. Lessons learned are produced at the end of a project, or they may take place between project phases to make the lessons learned available for later phases.

The lessons learned tool would assist the project team to identify and document lessons learned. The tool provides guidelines and questions to consider about what worked well, what did not work well, and what needs to be done differently. The goal of documenting lessons learned is to identify both the positive and negative lessons learned from the project, as well as to recommend corrective actions based on negative lessons learned remarks

The lessons learned tool provides general guidelines for accurately documenting the project lessons learned. Additional examples and suggestions are provided to help you produce your lessons-learned project deliverable.

Template style conventions are as follows:

Style

Convention

Normal text

Indicates placeholder text that can be used for any project.

[Instructional text in brackets]

Indicates text that is to be replaced/edited/deleted by the user]

Example text in italics

Indicates text that might be replaced/edited/deleted by the user

As you us this tool, please remember to delete all instructional text (including this section) and update the following items, as applicable:

· title page

· version history

· table of contents

· headers

· footers

Introduction

[Provide a brief description of the purpose of lessons learned and details of what is included in the document. Feel free to make any assumptions as you feel necessary. Keep in mind the project for this course only addresses the planning for the PPM Selection, and does not address any execution, monitoring, and controls considerations. Hence, any lessons learned in your document need to address the scope of your project, and only address planning. Reference to below an example introduction. Feel free to conduct your own research and inform this section as you feel appropriate.

Lessons learned allow a project team to retrospectively contemplate and document the failures and successes experienced on a project to facilitate the knowledge transfer from one team to the next. Capturing this information in a formal fashion creates an artifact that can be utilized during future endeavors to reduce the risk of repeating a mistake. This lessons-learned document includes input from the project team as to what went well, what did not go well, why, and what could have been done differently.

Lessons Learned Approach

[Describe the process that was utilized to capture these lessons learned, including the approach (such as brainstorming, surveys, interviews, and self-reflection), and what types of information were gathered.]

Lessons Learned to identify and delineate considerations taking into consideration the following categories:

· Cost

· Communication

· Documentation

· Processes

· Procurements/Contracts

· Quality

· Resources/Staffing

· Schedule/Time

· Scope/Requirements

· Tools

To encourage the thought process, you are encouraged to answer the following questions.

· What worked well for this project?

· What did not work well for this project?

· What could have been done over or differently?

· What surprises did you deal with?

· What project circumstances were not anticipated?

· Were the project goals attained? If not, what changes need to be made to meet goals in the future?

All lessons learned are documented in the table below.

Lessons Learned Table

[Complete the following table. Identify the categories as needed (such as cost, communication, documentation, processes, procurements/contracts, quality, resources/staffing, schedule/time, scope/requirements, and tools), the lesson learned, a description of the lesson learned, and a recommendation to implement the lesson learned.]

The lessons learned table provided below serves as an example only. Feel free to inform this table as you feel necessary.

ID

Process Phase

Category

Lesson Learned

Description

Recommendation

1

Planning

Resources

Not enough staff

The Planning Process Phase for this project took significant effort to develop plans and methodology and to navigate the Project Approval Lifecycle. Only one resource was allocated for this work.

The full scope of activities during the Planning Process Phase needs to be taken into consideration when resourcing the work. If additional resources are not available, the schedule must be pushed out.