Actually the most effective strategy I've seen is Kanban, but with a fixed release deadline.
Inevitably there are some essential tickets and some nice-to-have tickets.
For the nice-to-haves it's a case of progress or die.
Think of it as time constrained Kanban with semi-fixed scope.
The dropped tickets may carry over to a later release (if there is one), or just die forever (make it easy to cull bullshit).
P.S. From this perspective, the first thing to die is the time wasting sprint rituals that Scrum layers on top of Kanban.
Think of it as time constrained Kanban with semi-fixed scope. The dropped tickets may carry over to a later release (if there is one), or just die forever (make it easy to cull bullshit).
P.S. From this perspective, the first thing to die is the time wasting sprint rituals that Scrum layers on top of Kanban.