3 ms·

I have the same experience with retros. Generally they've have been a waste of time. Any useful information that could have been gleaned from them were probably

I have the same experience with retros. Generally they've have been a waste of time. Any useful information that could have been gleaned from them were probably already had in an earlier discussion, tend not to be remembered to be brought up again in retros, and at least in the teams I've been on the minutes from the retro meetings don't get recorded anywhere anyway, so there's nothing to refer back to in the future.

pas 4y ago
it seems these teams lack(ed) the drive to consciously change. meetings should have conclusions (action items based on consensus, which are commitments from all members) and it's a typical team dysfunction when members don't honor commitments (someone doesn't do something and then others don't bring this up to hold each other accountable) if the team is so dysfunctional that it just does the same thing over and over again while constantly promising to change then it should be broken up before the members themselves start to suffer the psychological toll of this cognitive dissonance.
- trhway 4y ago
  >it seems these teams lack(ed) the drive to consciously change. classic Scrum statement - putting the blame again on teams. A team usually has no power to change anything that matters.
  - pas 4y ago
    what has this has to do with scrum? I haven't even mentioned it (or even implied that this has something to do with scrum), dysfunctional teams are waaaay more general problem than whatever scrum is/isn't. Blame implies responsibility, which - like you mentioned - is not that simple. (Depending on personal philosophy maybe each team member has a responsibility toward themselves to get a job where they are not put into the aforementioned loony toones situation, but even with that in mind I honestly think you misinterpreted my comment, because I don't meant to assign blame at the team and its members. You might notice I expressly mentioned that if the team is too dysfunctional it has to be broken up "from above", implying that its not the responsibility of the team.)
urthor 4y ago
Disagree. After retrospectives we've always had a pretty good idea of what our problems are. Motivation to fix those issues is a different story. Scrum can't solve for lacking motivation.

pas 4y ago

it seems these teams lack(ed) the drive to consciously change. meetings should have conclusions (action items based on consensus, which are commitments from all members) and it's a typical team dysfunction when members don't honor commitments (someone doesn't do something and then others don't bring this up to hold each other accountable) if the team is so dysfunctional that it just does the same thing over and over again while constantly promising to change then it should be broken up before the members themselves start to suffer the psychological toll of this cognitive dissonance.

trhway 4y ago
>it seems these teams lack(ed) the drive to consciously change. classic Scrum statement - putting the blame again on teams. A team usually has no power to change anything that matters.
- pas 4y ago
  what has this has to do with scrum? I haven't even mentioned it (or even implied that this has something to do with scrum), dysfunctional teams are waaaay more general problem than whatever scrum is/isn't. Blame implies responsibility, which - like you mentioned - is not that simple. (Depending on personal philosophy maybe each team member has a responsibility toward themselves to get a job where they are not put into the aforementioned loony toones situation, but even with that in mind I honestly think you misinterpreted my comment, because I don't meant to assign blame at the team and its members. You might notice I expressly mentioned that if the team is too dysfunctional it has to be broken up "from above", implying that its not the responsibility of the team.)

urthor 4y ago

Disagree. After retrospectives we've always had a pretty good idea of what our problems are. Motivation to fix those issues is a different story. Scrum can't solve for lacking motivation.