6 ms·

Do you find that having so much positivity in your retros silences voices that might be going against the status quo? Serious question. We've been struggling i

by aynsof 10y ago

Do you find that having so much positivity in your retros silences voices that might be going against the status quo? Serious question. We've been struggling in our recent retros to find any negatives to talk about, and I've been trying to make sure we're not averse to making suggestions that might feel like complaints.

rebeccaemgreen 10y ago
I haven't noticed it, if it happens. We have a pretty good mix of topics in our list, both happy things and painful things. We complain a lot, and maybe that didn't come through because the retro meeting and the retro email are separate, and the email only focuses on the happy stuff. We're definitely not averse to complaining! For example, when someone writes a spec that fails randomly, that definitely gets brought up, because it affects everyone's productivity. Someone usually volunteers to help fix it, and we circle back at the next retro to make sure that it's been fixed. Complaining is A-OK as long as you're also committed to finding solutions!
Mz 10y ago
It seems to me if there are actionable items that come out of it, then it will be productive. It is often possible (though not natural for most people) to frame a complaint or criticism in more positive terms. In other words, "I don't like X" can become "We should do Y to make X better." Most people have no trouble being critical. Getting away from that tends to be hard work and can make it easier to accomplish things. /2 cents
civilian 10y ago
Are your retros a small enough group? I am more reticent to bring up negative stuff, especially if it's mostly about myself, if my boss's boss, marketing people, lead of product, and the finance person are all sitting in on the retro. If it just manager, project manager and the rest of the engineering team, then I feel way more comfortable sharing in that kind of safe space.
- rebeccaemgreen 10y ago
  this is so important! Our retros are just engineers & engineering-adjacent people (data, design, product managers). My boss sometimes comes to the meeting, his boss doesn't. I think our vp also comes sometimes, but he was one of the first engineers and is always open to feedback, so it's not like "the boss is in the room, we have to be on our best behavior"
  - rebeccaemgreen 10y ago
    replying to myself because this is near and dear to my heart: we also do individual team retros as part of sprint planning, which are just teams. (lead, engineers, product manager) Stuff that comes up in these can get promoted to the all-engineering retro. If it's a controversial topic, discussing it in a small group is super helpful because 1, you can clarify your thinking before bringing it up in front of 30 people and 2, your team has your back and can support you if it becomes a heated discussion.
    - civilian 10y ago
      I know you replied 7 days ago, but I've kinda had a crazy week. Having a separate individual team repo definitely sounds good, and I like the idea of things "bubbling up". Things probably do bubble up at my team already, but I imagine my manager shields me from that stuff. Which I'm not sure if I love.

by aynsof 10y ago

rebeccaemgreen 10y ago

I haven't noticed it, if it happens. We have a pretty good mix of topics in our list, both happy things and painful things. We complain a lot, and maybe that didn't come through because the retro meeting and the retro email are separate, and the email only focuses on the happy stuff. We're definitely not averse to complaining! For example, when someone writes a spec that fails randomly, that definitely gets brought up, because it affects everyone's productivity. Someone usually volunteers to help fix it, and we circle back at the next retro to make sure that it's been fixed. Complaining is A-OK as long as you're also committed to finding solutions!

Mz 10y ago

It seems to me if there are actionable items that come out of it, then it will be productive. It is often possible (though not natural for most people) to frame a complaint or criticism in more positive terms. In other words, "I don't like X" can become "We should do Y to make X better." Most people have no trouble being critical. Getting away from that tends to be hard work and can make it easier to accomplish things. /2 cents

civilian 10y ago

Are your retros a small enough group? I am more reticent to bring up negative stuff, especially if it's mostly about myself, if my boss's boss, marketing people, lead of product, and the finance person are all sitting in on the retro. If it just manager, project manager and the rest of the engineering team, then I feel way more comfortable sharing in that kind of safe space.

rebeccaemgreen 10y ago
this is so important! Our retros are just engineers & engineering-adjacent people (data, design, product managers). My boss sometimes comes to the meeting, his boss doesn't. I think our vp also comes sometimes, but he was one of the first engineers and is always open to feedback, so it's not like "the boss is in the room, we have to be on our best behavior"
- rebeccaemgreen 10y ago
  replying to myself because this is near and dear to my heart: we also do individual team retros as part of sprint planning, which are just teams. (lead, engineers, product manager) Stuff that comes up in these can get promoted to the all-engineering retro. If it's a controversial topic, discussing it in a small group is super helpful because 1, you can clarify your thinking before bringing it up in front of 30 people and 2, your team has your back and can support you if it becomes a heated discussion.
  - civilian 10y ago
    I know you replied 7 days ago, but I've kinda had a crazy week. Having a separate individual team repo definitely sounds good, and I like the idea of things "bubbling up". Things probably do bubble up at my team already, but I imagine my manager shields me from that stuff. Which I'm not sure if I love.