Funny you mention that. I was going to say "oh no. you can do Kanban with Jira," but then I remembered that every place I've seen that "does Kanban" is really

Funny you mention that. I was going to say "oh no. you can do Kanban with Jira," but then I remembered that every place I've seen that "does Kanban" is really doing some local spiral-waterfall-esque process, but using the Kanban board on Jira. And even those are using Kanban without telling their management chain because their management chain would freak out because they can't spell Kanban and after going to "Scrum Camp for Managers," they at least know how to spell Scrmu. (very clearly this is not all managers. I've had the pleasure of working with several people who really know what they're doing. But I think it's all to often you find a stunned management chain who's trying to make sense of Scrum.) I should have been clearer as to what my point was: Just 'cause you're using the tool (Jira) does not mean you're automagically using the process (Scrum). And maybe a related side-point: Scrum (like Agile) is a way of thinking about software development. Not everyone gets that. That might be the value of a good Scrum-Master. I've yet to see a good Scrum-Master in the wild. Most of the ones I've encountered are just dudes who tweak Jira settings half the day and use the other half of the day poking at Jira's SQL schema so they can fix config errors they made before they learned how the current version of Jira works. Or... in other words... if you're only filling out Jira tickets and only doing the ceremonies, then you're leaving half of Scrum's value on the table. Too many people do this.