Agile Tutorial: How to Conduct Project Retrospective

What is project retrospective?

At project closure, conduct a project retrospective meeting with the scrum core team to determine ways in which project team can be improved in future projects. Collect both positive and negative feedback from the participant and capture the lessons learned.

Perform the steps below to conduct a project retrospective meeting.. You may try the steps interactively by visiting the interactive product tour.

Step 1: Prepare for a project retrospective meeting

  1. In the Scrum Process Canvas, click on the work item Project Retrospective Meeting to open it.
  2. As the first step, you are required to prepare the project retrospective meeting by deciding the date and time, the attendee and the agenda of the meeting. Click on the action artifact Project Retrospective Meeting.
  3. Fill-in the meeting form to complete this step. First, specify the background of the meeting by entering the date, time, location of the meeting. Besides, select the members who will attend the meeting.
  4. List the topics to be discussed in the meeting as agenda topics. Press Enter to create a new topic.
  5. Enter other information such as the observers and resources required.
  6. When finished, go back to the work item page via the breadcrumb.
  7. When you are done, you can move on to the next step. To do this, click on Complete Step at the bottom right corner, and then select Complete from the popup menu.

Step 2: Capture project’s key successes

You are now in step 2. In this step, you will capture the key successes achieved by the project.

  1. Click on the action artifact Project Key Successes to continue.
  2. Fill-in this form to complete this step. First, list the major success achieved by the project.
  3. Describe the factors that contributed to those successes. Instead of just describing the successes the project has had, it’s more valuable to state the factors that contribute to these successes so that similar projects can repeat the successes.
  4. When you are done, go back to the work item via the breadcrumb.
  5. Complete this step to move on to the identification of project challenges.

Step 3: Capture project’s challenges and shortcomings

  1. Click on the action artifact Challenges and Shortcomings.
  2. Project challenges refer to the conditions, not under the control of the project team, which affects the project negatively. Complete this part first. Discuss and list out the major challenges one by one.
  3. Describe them and recommend solutions. A recommended solution can be one that’s implemented and found effective. It can also be a better alternative of the implemented option.
  4. List the major project shortcomings. Shortcomings are the tasks that were done wrongly or poorly, or any decisions made incorrectly. It’s sometimes confused with challenge and difficulty, yet it is neither. To make it simple, challenge and difficulties are adverse situations that require resolving in order for the project to complete, while shortcomings are fault and failures.
  5. Again, describe the items and recommend solutions.
  6. Document the things that the team would/could do differently next time to improve or mitigate the difficulties as a whole (more holistic and strategic in nature).
  7. When finished, go back to the work item via the breadcrumb.
  8. Complete this step.

Step 4: Wrap up the meeting

In the final step, you have to wrap up the meeting by entering the discussions and conclusions of the meeting and creating tasks to address problems and improve processes in order to enhance their performance in future projects.

  1. Click on the action artifact Project Retrospective Meeting.
  2. Complete the meeting form. Describe the discussion and conclusion for each agenda topic.
  3. When finished, go back to the work item.
  4. Complete this step.

Turn every software project into a successful one.

We use cookies to offer you a better experience. By visiting our website, you agree to the use of cookies as described in our Cookie Policy.