You don't need Scrum. You just need to do Kanban right (2022)

Re:You don't need Scrum. You just need to do Kanban right (2... by pg_1234 on Monday May 08, 2023 @04:36AM (#35859384)

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.

P.S. From this perspective, the first thing to die is the time wasting sprint rituals that Scrum layers on top of Kanban.

[ Parent | on HN ]

Re:You don't need Scrum. You just need to do Kanban right (2... by vikingerik on Monday May 08, 2023 @11:16AM (#35862524)

That's functionally scrum anyway, you're just not calling it that to avoid the ceremony, yeah.

[ Parent | on HN ]

Re:You don't need Scrum. You just need to do Kanban right (2... by kahmeal on Monday May 08, 2023 @12:44PM (#35863793)

The ceremony just undoes the efficiency in most cases; That's the rub.

[ Parent | on HN ]

Re:You don't need Scrum. You just need to do Kanban right (2... by pg_1234 on Monday May 08, 2023 @05:52PM (#35867487)

No that's not scrum, as any "scrum master" will tell you ... scrum imposes it's own artificial cadence.

This is kanban ... just culminating in a release event anything from weeks to months in the future (driven by time factors independent of dev management i.e. actually having to produce something as a business). I mean nobody can seriously be proposing no time bound on kanban (please clear the board this decade?)

If you're behind schedule pausing for a ridiculous high school level show and tell will only delay you more ... and if you're ahead of schedule, just keep doing what you're doing right.

What kanban provides is visibility, how much you're getting done. Scrum sacrifices momentum for theatre.

[ Parent | on HN ]