3 ms·
Hoping this is hyperbole, but if your reviews or retrospectives are actually four hours long, you should politely point out that these do not need to be more th
by eastbayjake 6y ago
Hoping this is hyperbole, but if your reviews or retrospectives are actually four hours long, you should politely point out that these do not need to be more than an hour (and many mature scrum teams do both in an hour total)
- trustfundbaby 6y agoWhy ... so you can be labelled a malcontent, non-team player, denied promotions and eventually managed out of the org at first opportunity? :)
- eastbayjake 6y agoThere is a way to give this feedback that is positive, collaborative, and highlights what a great team player you are -- the sort of thing that gets people promotions. But YMMV!
- pelasaco 6y agoit's unfortunately not a hyperbole. It takes us literally 4 hours. Mostly the scrum master do it as a monologue. We all just zoom out and do other stuff. Last sprint i finished a lib that i was working on and deployed our code twice in production to avoid dying live on teams.
- gamacodre 6y agoInteresting. It usually takes us most of an hour to get through our reviews, and I don't feel like we have an unusually high number of deliverables (10-15 tickets on average maybe, representing 1 or 2 larger projects and a small batch of regressions/spikes/featurelets, for a 3-dev team). Retros are taking around an hour, faster than last year by 2x but the time still feels like it's well-spent.