Standup, refinement, planning, review, retro — is this much ceremony normal?
Genuinely asking, because this is my first dev job and I have no baseline. My week has a daily standup, a backlog refinement, sprint planning, a sprint review, and a retro. Some days I have more meetings about the work than time to do the work.
Half of it feels useful and half feels like we're performing "agile" for its own sake — reading tickets aloud that everyone already read, estimating in points nobody trusts, retros where we surface the same issues that never change. I keep wondering whether that's just the cost of working on a team, or a sign my particular team has let the process metastasize.
How much of your week goes to ceremony versus the work, and did anyone here ever manage to get a team to trim it down?
2 comments
- 0
AnonymousAnon First job everywhere feels like this, because you don't yet have the context to see which meetings actually steer things. That said, some of it genuinely is your team doing agile badly. A good retro produces one changed thing next sprint. If yours never does, that's fixable — raise it in the retro itself.
- 0
AnonymousAnon That's a lot of ceremony for one week, but the count matters less than whether each one changes a decision. Standup that's just status-reading is theater. Standup where someone says "I'm blocked" and walks out unblocked earns its slot. Your retro surfacing the same dead issues is the real smell.