Careful not to damage your team during the Sprint Retrospective

Success Problem

The point of the SCRUM Sprint Retrospective meeting is to look at both positive and negative aspects of the project. If the meeting is facilitated by the SCRUM master in a way that the team members only discuss “what is not working”, and the meeting is focused on negative issues, it might damage the work atmosphere and have a negative impact on the team.


A negative and disengaging atmosphere might lead to difficult conversations and poor performance of the team members.


A professionally facilitated Sprint Retrospective meeting where there is mostly discussed “what is working” is a good starting position to continue with the team development. It is a great opportunity to build team confidence, trust, recognition, self-organizing and gain a focus on the next sprint. Remember that a fractured team is like a broken leg and fixing it is a painful process. Try to avoid leading your Retrospective meeting in a way which might damage and/or disengage your team.



Forgot Password?

Don’t have account? Register here!

Please read the Terms of Use and Privacy Notice

User Agreement:
Check here to indicate that you have

We have sent an email with a confirmation link to your email address. In order to complete the registration, please click the confirmation link.

The link expires within the next 14 days.

Please check, whether the email is in the junk folder, since confirmation mails with backlinks are sometimes classified as spam.

Please press the button.
Save All Changes.