Project Closing Actions

Bill Carmody explains the importance of conducting a retrospective at the end of a project. He outlines the steps to set up a retrospective, including gathering feedback from all participants. The purpose of closing actions is to document insights and learnings, ensuring that knowledge is captured and shared for future projects. This process helps improve future projects by learning from past experiences.

What is the primary purpose of conducting a project retrospective?

• To assign blame for any failures

• To finalize the project budget

• To gather feedback and insights for future improvements

• To celebrate the project's success

Which of the following is NOT a question typically addressed in a retrospective?

• What worked well in the project?

• What can be improved?

• What remains puzzling or unknown?

• What is the next project's budget?

Why is it important to document the insights gained from a project?

• To increase the project's budget

• To help future projects benefit from past learnings

• To make sure the project is remembered

• To ensure the project manager gets a promotion

What should be done with the knowledge gained from a project?

• It should be kept secret

• It should be discarded after the project ends

• It should be used to criticize team members

• It should be documented and reviewed

How can future projects benefit from a retrospective?

• By focusing only on successful elements

• By repeating the same processes without change

• By reading up on what worked and what didn't

• By ignoring past mistakes