3 ms·
well yes, assignment is fine, but given eng's limited bandwidth and the product's conflicting priorities mean the action items coming out of retros are depriori
by pypudding 2y ago
well yes, assignment is fine, but given eng's limited bandwidth and the product's conflicting priorities mean the action items coming out of retros are deprioritized, unless someone can really make a case for them.
- dave4420 2y agoProduct people take part in your retros, right?
- pypudding 2y agoWe had three kinds of retros - product(half an year), sprint(monthly), incident(per rotation). Yes product folks join the first one, but definitely not the more frequent engineering retros, which is also where the mentioned issues surface faster, also is taking the most time. How's it like for you?
- dave4420 2y agoSpeaking generally (as I am currently between roles) the whole team always comes to retro, including the team’s product person. Sometimes external people (e.g. from Customer Success) have been invited as well. And I’ve never seen any problem getting buy in from product. I honestly think restricting retros to the engineers on a team is too narrow. Most places I’ve worked this has been fortnightly.
- pypudding 2y agoThat's nice. AFAIK SRE retros are harder to get product buy ins. It could really depend on the team and the service they provide...