Skip to main content
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
4 votes
Accepted

Is it better to revitalise or restart a project that has been modified?

Since you are in agile, I would treat this as new information discovered about the project and change/update User Stories / sub tasks. You are still doing a website development, so the basis of the ...
Marcus D's user avatar
  • 461
3 votes

Is it better to revitalise or restart a project that has been modified?

Putting scrum aside, is the application written in a flexible manner? Although scrum welcomes change, the way the application was written should be flexible as well up to some extent. if it is too ...
newbie programmerz's user avatar
3 votes

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

The Scrum team alone cannot solve every impediment. It is a good idea to have some kind of escalation path for issues that are outside of the control of the team, but are recurring and damaging. As a ...
Barnaby Golden's user avatar
2 votes

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

A retrospective should not ban topics. And a retrospective must not waste people's time, either. With that said, what you could do is categorise the retrospective items according to different ...
Tiago Cardoso's user avatar
  • 8,653
1 vote

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

If the same impediment is being raised Sprint after Sprint, that brings up a few questions. Is someone actively working on resolving the impediment? Maybe it can't be resolved within the Scrum Team ...
Thomas Owens's user avatar
  • 19.6k
1 vote

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

Censoring an impediment from the retrospective doesn't solve it. As it looks to be a major impediment that's blocking the team, maybe it's worthwhile to arrange a separate meeting to analyze the ...
BenLinders's user avatar
1 vote

Actions to improve Scrum Restrospective

Here are few suggestions, which you can bring together or one-by-one. SUGGESTION 1: Bring awarding best team member of the sprint in your Retro: Ask the team to vote during Retro Collect vote in ...
Barani's user avatar
  • 91
1 vote
Accepted

Actions to improve Scrum Restrospective

Indeed Retromat is very inspirational for spicing up the Retrospectives for your developers. But at some point I faced the same issue of minor effectiveness in my team -after one year of working ...
axel's user avatar
  • 389
1 vote

Actions to improve Scrum Restrospective

I'd look at the 5-stage retrospective approach. Retromat provides a lot of different activities that you can use for each stage. Also, there should be experimental changes (usually limited to 1 or 2) ...
Daniel's user avatar
  • 16.9k

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