DEV Community

Discussion on: How many meetings do you have per week?

Collapse
 
ekeijl profile image
Edwin
  • Daily stand-up (15-30m) - useful, quick status updates and discuss urgent issues.
  • Weekly architecture discussion (1h) - cross-team discussion of any architecture topic, this is good for standardisation across teams, reach consensus on topics.
  • Biweekly sprint review (1-1.5h) - Every team presents work delivered during the sprint, useful to see progress and gives devs a feeling of closure.
  • Biweekly feature kickoff(1.5h) - PM presents new features and collects some early technical feedback from the team (helps the team get a feeling of what's coming and understand the bigger picture).
  • Biweekly sprint planning (1-2h) - estimate planned work for the coming sprint, assign story points and identify any issues before work is started.
  • Biweekly retrospective (1h) - feedback on internal processes, which does help to improve over time.

Finally there are functional/technical refinement meetings (1h each, as many as needed) where a small team prepares user stories, define requirements, raise issues in spec/architecture/etc before it is planned for the next sprint.

Sometimes it feels like a lot, but if we don't have these meetings, then devs would have to figure this stuff out during a sprint and the overall delivery time would be longer. So most of them are useful planning meetings, which can be tedious, but we try to limit to 1h so everyone stays sharp.