Skip to main content
34 votes
Accepted

Is it a good idea to show a 'story points by developer' graph at retrospectives?

TLDR: The team should be a team. We are not 'shamed' [...] developers don't want to look bad See the problem here? Whether or not your developers are being 'shamed', your developers are afraid of ...
Sarov's user avatar
  • 14.8k
28 votes
Accepted

Should I ask my boss not to come to retrospectives?

It sounds like you have team members from high power distance cultures. People may not speak up when the boss is in the room because their values require them to listen and follow, not to advise or ...
Jake Vosloo's user avatar
16 votes

Manager no longer invited to the retrospectives

This is a tough situation. Since the manager does work with the team on the delivery of product Increments, the manager is a member of the Development Team. Because of this, the manager should be a ...
Thomas Owens's user avatar
  • 19.6k
16 votes

Should I ask my boss not to come to retrospectives?

Analysis There is a chilling effect when he is here. Am I overreacting? Should I just try to build up the confidence of the team? or should I ban my boss from the retrospective? In my experience, ...
Todd A. Jacobs's user avatar
  • 50.5k
14 votes

Is gauging a team's performance using scores assigned by other stakeholders valuable?

There is nothing wrong with this type of scoring. This type of customer confidence score is the same general idea as NPS and a multitude of other score. Whether or not it is healthy is largely ...
Daniel's user avatar
  • 16.9k
13 votes
Accepted

Is gauging a team's performance using scores assigned by other stakeholders valuable?

Do other companies do this? Is it considered Agile? Can it show real insight? No. No. No. Why not? Because it's completely pointless. You said you have sprints. I guess they have tickets or stories ...
nvoigt's user avatar
  • 8,525
13 votes

Agile Retrospective: Comments Anonymous?

The retrospectives I facilitate are not anonymous. If a team member asked me to allow anonymous comments I would certainly do so. I would then try and investigate why psychological safety was so low ...
Barnaby Golden's user avatar
12 votes
Accepted

Product Owner is requesting a "confidence check" for reaching the MVP - How to in a Scrum project?

While such a confidence check is nothing that you'd read about in Scrum Guide I don't see it as something that violates Scrum in any way. It is, in fact, answering a different question: the one about ...
Pawel Brodzinski's user avatar
12 votes

Manager no longer invited to the retrospectives

There are two things to comment on here: Can the Scrum Master exclude somebody from a Scrum ceremony? Should the Scrum Master exclude somebody from a Scrum ceremony? On the first question, a Scrum ...
Barnaby Golden's user avatar
12 votes

Is it a good idea to show a 'story points by developer' graph at retrospectives?

TL;DR Your organization is fundamentally misusing the story point metric, and also conflating story points with velocity (which is also being misused). Please stop doing those things before you ...
Todd A. Jacobs's user avatar
  • 50.5k
11 votes

What should a team do in the Sprint Retrospective when everything is going well?

Retrospectives: For Continuous Improvement The misunderstanding of the retrospective as a place to fix problems is very common. However, the goal of the retrospective isn't just to discuss problems; ...
Todd A. Jacobs's user avatar
  • 50.5k
11 votes

No retrospectives in software company - Is this a bad sign?

TL;DR: Maybe you're having a XY problem. Retros are a tool for a means, not a means in itself. As yourself: Why are you asking around if the team has retros? Chances are, this question is a shortcut ...
Tiago Cardoso's user avatar
  • 8,653
10 votes
Accepted

Daily Standup, Demo, Retrospective - Mandatory? How?

There are two parts to the Scrum Master role: Helping the team to resolve impediments Ensuring that Scrum is being followed The second part often gets neglected, but it is very important. If the ...
Barnaby Golden's user avatar
10 votes

Team needs a lot of time to deliver even the simplest stories- how to know why?

...a lot of time to deliver even the simplest stories Only the development team knows what constitutes a simple story. The time it takes to deliver a story depends on a lot of factors, including: ...
Barnaby Golden's user avatar
9 votes

Manager no longer invited to the retrospectives

If this manager is part of the team and codes and completes tickets in the team's sprint, then he needs to be at the retrospective meetings. Your Scrum Master screwed this one up by uninviting him. ...
Bogdan's user avatar
  • 15.2k
7 votes

Retrospective - too many small and random problems. Death by a thousand needles

Technical Debt is Often Invisible The problem with technical debt isn't just that it's there. The bigger problem with such debt is that it becomes a "missing stair" that everyone steps around and ...
Todd A. Jacobs's user avatar
  • 50.5k
7 votes

What is meant by "inspect people" in Scrum retrospective guide?

The key with retrospectives is to focus on potential improvements, not on problems. As you rightly say, "John was not performing well during the sprint" is not great language. However, the team might ...
Barnaby Golden's user avatar
7 votes

How should we implement and keep track of recurring or intangible retrospective action items?

What I find an effective way to keep those kinds of "behaviour change" actions under the attention of the team is to hang them next to the kanban board, large enough that they can be read from a ...
Bart van Ingen Schenau's user avatar
7 votes

How do you make the Teams Retrospective Actions visible and ensure they get attention throughout the Sprint?

Retrospective actions are a vital part of the Sprint work, so they should be agreed with PO and tracked as such. You mentioned you use a Kanban board. Why not tracking each action as an item in the ...
Tiago Cardoso's user avatar
  • 8,653
7 votes

Is it a good idea to show a 'story points by developer' graph at retrospectives?

I worked in an organisation some years back that decided to try and do performance reviews based on the number of story points delivered by individual developers. It was a complete disaster: the ...
Barnaby Golden's user avatar
7 votes
Accepted

As a Scrum Master, how to speak to a developer about his delays?

Any suggestions ? I'm sure there is an official Scrum answer and a project management answer. This is a common sense workplace answer: Don't bother. That person is out of the door. They are there ...
nvoigt's user avatar
  • 8,525
6 votes

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

Is this a standard or good practice in facilitating a retro to 'censor' known issues like this? Yes and no. I feel it's wrong to censor anything, especially talking about impediments at a ...
nvoigt's user avatar
  • 8,525
6 votes

Quicker Retrospectives? They are taking longer and are less effective now we are working from home because of COVID

The first item in the Agile Manifesto is: Individuals and interactions over processes and tools Your question lists a bunch of tools and asks about more tools, some that are more flexible to use ...
Bogdan's user avatar
  • 15.2k
5 votes
Accepted

How to encourage more participation in web scrum meetings?

In my experience periods of silence in a retrospective are caused by the following: The team sees no value in the retrospective The team is too large and people are uncomfortable talking The team has ...
Barnaby Golden's user avatar
5 votes
Accepted

Should issues with individuals be called out in retrospectives?

I'm sorry to see that this has been going on for months. Did it ever come up in the retrospective? During stand-ups? Since it seems to be hampering the team I would have expected that one or more team ...
BenLinders's user avatar
5 votes

Should issues with individuals be called out in retrospectives?

Go with Mantra: "Praise in public. Criticize in private" In retrospection, concentrate on processes rather than individuals.
Barani's user avatar
  • 91
5 votes
Accepted

Toxic Retrospective in Agile Development

Getting a little meta (no not that meta) here, but... This should be discussed in the Retrospective. You state: one of our Team members has been passive-aggressively launching personal attacks on ...
Sarov's user avatar
  • 14.8k
5 votes
Accepted

What is an Agile "Reflection?"

I would imagine it is related to the 12th agile principle: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly". Reflecting is ...
5 votes
Accepted

Carrying items over from one sprint to the next

There is a lot in there, so let's take it item by item. First, what do we do with incomplete work? It goes back to the product backlog. Technically, the product owner decides if it is still ...
Daniel's user avatar
  • 16.9k
5 votes
Accepted

Large group retrospective format

You can define the topics to be discussed up front, based on data collected and affinity diagrams as you suggest. That would make it easier for participants to prepare. But you can also have the ...
BenLinders's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible