HACKER Q&A
📣 volkk

Team misusing sprints, kanban makes more sense. How to switch?


My team uses sprints and I'm realizing our need doesnt really match how sprints work. Nothing gets cut, we end up just moving everything over to the next sprint over and over until the features are complete. Sprint plannings are mostly a waste of everyone's time as nothing valid happens beyond ticket assingment (except everyone already mostly knows what they should be working on)

The only super useful meetings we have is grooming where we talk through each ticket within each respective discipline.

I am looking into kanban which feels a lot more "right" to our workflow. Wondering for those of you who are using kanban, what is the difference, assuming you've done your classic scrum stuff in the past.


  👤 verdverm Accepted Answer ✓
Have retros where you talk about the process and how stories went from a high level. What went well, what went poorly, what should we keep doing or change. Process improvements will emerge organically.

In the end, these are just tools and processes to help you deliver a product. How are you doing at delivering product? Does the way it is done today really hinder this or is this about an attachment to a "correct" agile process?


👤 cloudking
It sounds like your team isn't breaking down stories into tasks small enough to complete in a sprint, and underestimating the effort involved. If you want to use agile, spend some time on this area otherwise you may was well switch to waterfall.

👤 yuppie_scum
How to switch? Just switch.

👤 readonthegoapp
will the managers be happy with you trying to out them out of a job?

Don't think so.