[jrowley]

I think scrum is great when you have following properties: - clear goals - not a lot of interruptions - tasks / projects are particularly timeline sensitive. - you want to measure output and plan initiatives far into the future

Scrum can also have a fair amount of overhead, all of the rituals, eg pointing tickets, refining the backlog.

Also daily standup / status updates for 12 people can be a lot of time.

When you have support queue, operational responsibilities and regular dev work all going on in the same time, you might find you're spending a lot of time trying to ensure some amount of work gets done in a sprint, while support burden / operations supersedes estimates, which then pushes work to next sprint. So the sprint effectively becomes meaningless, because there is always lots of carry over.

Kanban does require a mature, self motivated team too though, since deadlines aren't as clear necessarily.