Q

In Agile retrospective, critiques aid growth

Negative comments or criticism in an Agile retrospective can lead to team growth.

In the Agile retrospective, are negative comments a bad thing? In other words, should we only allow positive comments...

in the retrospective?

Negative comments in the Agile retrospective are not bad. They are opportunities for discussion, agreement and improvement. By allowing only positive comments, you're avoiding issues, and avoidance prevents the team from growing and developing.

Negative comments should be allowed in the Agile retrospective when they are phrased professionally. A team that is forming and growing but can't be honest with one another has a problem. Avoiding issues is not going to help team development.

By allowing only positive comments, you're avoiding issues, and avoidance keeps the team from growing and developing.

I have been on a team where we've had comments that point out how people sometimes ignore professional etiquettes and talk over each other in meetings so that the loudest person is the only one who is heard. The majority of the team members were guilty of not allowing others to finish speaking. We were in such a hurry to have our thoughts heard that we were interrupting each other.

When this comment came up, it wasn't pointed toward anyone in particular but at the team as a whole. We realized it applied to all of us. If your team members have negative comments, just ensure they are not personal but are constructive for the whole team.

A team that has more than one member is going to generate negative comments; that's human nature. As long as comments are directed at the team or even a role, then I think that is constructive. If comments in the Agile retrospective become attacks against specific individuals, then I'd suggest taking the folks involved aside and helping them resolve their conflict.

If you need to involve human resources, then do it. Any personal issues need to be resolved one way or the other before the team can grow together. But ignoring all negative items is not the way to develop a solid, high-functioning team.

This was last published in May 2014

Dig Deeper on Software Project Management Process

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Retrospectives are a safe place where team members can bring up anything that's on their mind, both negative and positive. If there are issues, then they should speak up to address them with the team. So yes, negative comments are a good things as the enable teams to deal with them and get issues out of the way.
Cancel

-ADS BY GOOGLE

SearchSOA

TheServerSide

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

Close