> Where Scrum wiggles its way into relevance is schedule. I use both ... Kanban for operations/IT/Support, Scrum for product development. > So scrum just ends

> Where Scrum wiggles its way into relevance is schedule. I use both ... Kanban for operations/IT/Support, Scrum for product development. > So scrum just ends up being a hack to generate time pressure on the component tasks. Yes, but also it let's you figure you are off track early in the project. Too many people let themselves be fooled into thinking that "we went off the rails for a few weeks but we're back on track now" without some kind of process to force you to acknowledge the problem.