4 ms·
this is so important! Our retros are just engineers & engineering-adjacent people (data, design, product managers). My boss sometimes comes to the meeting, his
by 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 agoreplying 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 agoI 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.