Are retros and reviews usually 2 hours long? 🚩🚩

not usually.

I guess technically it's possible. Say the person went to lunch during Review, or that there's a lot of things he doesn't understand and keeps consulting pieces of code with you or others, maybe googling alternative solutions, maybe he's testing a better solution before recommending it to you... there's possible time-sinks during Reviews...

The most likely thing is that the person is just doing something else, maybe got assigned different work or just doesn't feel like doing the Review anymore and just is watching youtube or something

@Hazarth I’ve moved into a new team and I’m quite taken back by the amount of meetings they have ! My old team in contrast had so few.

@Burgundxyz meetings are the endless killer of productivity :(

Retro - 1 hour tops

Review - 30-60 min, but depends on how much actually went wrong and how much was done.

Some places or even teams have so many meetings in the name of agile they destroy the bit where you get any work done.

Depends on a few factors:
1. how new is the team to Agile. newer is longer.
2. how many team members are in the team. also, non team members in the room.
3. Ability to stay focused on the meeting purpose.

@C0D4 Most new Agile teams use the 2w pattern. They then forget to calculate meetings time: 10*.25h daily + 1h planning + 1h retro + 1h grooming + 1h demo = 6.5h Agile meetings per sprint - minimal. If something is longer, then you waste 1 day per sprint on meetings....

It's just time, and time is just money.

@magicMirror I'm yet to see a team include the ceremonies into the sprint time, let alone the additional 5 - 50 meetings through the week.

Yes, I've peeked at 50 meetings in 1 week, and then expected to still deliver that sprints work.... somehow.

Apparently we can multitask 24-7.

I'm not saying it doesn't exist, I just haven't found it.