13. A software project team is participating in a lessons learned review. One of the team members mentions that they were able to complete most of their tasks on time. They credit this to having taken into account previous projects' lessons learned with regards to time estimations.

Answer: B

Explanation:

What did we do right?

The team member's acknowledgment of their ability to complete most tasks on time, attributing it to lessons learned from previous projects, highlights a positive outcome. This reflects a key aspect of the lessons learned review, which is to identify and reinforce successful strategies.

A) What went wrong?

This option is incorrect as it focuses on identifying failures or mistakes rather than celebrating successes. The context provided indicates that the team was successful in their time management, making this question irrelevant to the discussion at hand.

B) What did we do right?

This option is the correct choice, as it aligns with the team's experience of successfully completing tasks on time by utilizing insights from past projects. Recognizing and discussing effective strategies is essential in a lessons learned review, reinforcing positive behaviors and practices.

C) How can we prevent what went wrong from going wrong next time?

This option is not applicable in this context, since the team member is discussing a success rather than a failure. Focusing on prevention of issues is important, but it does not address the current success being highlighted by the team.

D) What can we do better?

While this option suggests a forward-looking approach to improvement, it does not directly relate to the positive outcome mentioned by the team member. The emphasis here is on past successes, making this question less relevant in the context of celebrating what went right.

Conclusion

The correct answer, "What did we do right?", emphasizes the importance of recognizing successful practices that contributed to the timely completion of tasks. All other options either misfocus on failures or suggest improvements where none are warranted, thereby failing to capture the essence of the team's positive experience in the review.