Providing Feedback to Team Members

Even if you've taken the often stated agile stance of getting rid of periodic performance reviews in your organization, it can still be helpful to provide people with some commentary on how their work is perceived by others in the organization.

I like to do this by focusing on what an individual can start doing, stop doing and continue doing.

I email various people who can comment on an individual's work. This might include other team members, their ScrumMaster and product owner, stakeholders, or even people outside the company the person may have worked with on a regular basis.

I ask each to tell me what they think the person should start doing, stop doing and continue doing.

I don't weigh any one reply too heavily and instead I look for common threads or patterns in their responses. For example, one reply I received said the person should stop being so defensive. Another reply said the same person was occasionally rude in meetings and gave an example. The example corroborated the person's defensiveness and I was able to counsel the person to become more aware of it.

There are a couple of advantages to this approach:

  • It's very action-oriented. The person can be given a couple of specific behaviors to change (either to start or to stop).

  • It includes an element of praise for what others value in the person's behavior (the continues).

  • It can be done quickly enough that it can be done frequently and for a larger number of people as may be necessary with flatter organizational hierarchies.

  • It doesn't rely solely on your own observations of a person.

I've successfully used this as a manager providing feedback to my employees and as a coach helping ScrumMasters and product owners interact with their teams. If you're in either role, you might want to consider giving it a try.

(Note: I also use these same three questions--What should we start doing? Stop doing? Continue doing?-- as a simple but effective way to conduct a sprint retrospective.)

Article artwork for Why you should consider stopping sprint reviews.
Article

Why you should consider stopping sprint reviews

Featured

For many teams, the sprint review has run its course and it’s time to stop doing them. Blasphemy?

Guide

Meetings

Featured

Scrum meetings help a Scrum Team plan, coordinate, inspect, and improve during each sprint. Scrum officially calls these events.

Stakeholders are gathered round a table filled with index cards indicating thumbs up or thumbs down for each product backlog item. Whenever possible, avoid using a sprint review as a sign-off meeting.
Article

The Sprint Review as a Sign-Off Meeting

Featured

Decide whether sprint reviews should be used as formal sign-off meetings.

Article artwork for Sprint Review Agenda.
Article

Sprint Review Agenda

Use a simple agenda to make sprint reviews more focused and useful.

Becoming a product owner is a big decision. Have you considered becoming a product owner? Maybe you should.
Article

Should You Become a Product Owner?

Explore the skills, paths, and tradeoffs to consider before stepping into the product owner role.

A series of arrows, each reading sprint, leads down a highway to a distant sign reading "product goal." One of a product owner's many responsibilities is to set a product goal: that next mile marker for the product.
Article

What Does a Product Owner Do, When, and Why?

Clarify what product owners do before work starts, during planning, and throughout each sprint.