this post was submitted on 15 Jun 2024
277 points (97.9% liked)
Programmer Humor
32461 readers
436 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm starting to think the way to go isn't set stories in the sprint at all. There's a refined backlog in priority order. You grab one, do it, grab the next. At the end of the two week period, you can still have a retro to see how the team is doing, but don't worry about rollover.
Alternatively, don't think of Agile as a set instruction manual, but rather a group of suggestions. Have problem X? Solution Y worked for many teams, so try that.
You basically just described kanban.
Ah yes. Life before Agile was wonderful.
Like traditional project management?
This is what I always say. Put the tickets in order and we'll do them.
Management always pushes back.