> Just 'cause you're using the tool (Jira) does not mean you're automagically using the process (Scrum).
Absolutely. No tool can successfully make the process. Its job is to make the process easier.
> That might be the value of a good Scrum-Master. I've yet to see a good Scrum-Master in the wild.
Let me share a secret. I'm a trained and certified Scrum Master. You're spot on about it being a way of approaching things more than anything else. Software development is in large part an exercise in complexity management, and the Agile approach is fundamentally a very useful way of conceptualizing how to manage complexity at a very high level of abstraction.
But as practiced, I've soured on it quite a lot. The ideal is... ahem... ideal, but what we tend to see is kind of a funhouse mirror version of it that, at best, isn't helping. Different flavors of Agile are better (Kanban) or worse (Scrum) about this, but it affects all to one degree or another.
Absolutely. No tool can successfully make the process. Its job is to make the process easier.
> That might be the value of a good Scrum-Master. I've yet to see a good Scrum-Master in the wild.
Let me share a secret. I'm a trained and certified Scrum Master. You're spot on about it being a way of approaching things more than anything else. Software development is in large part an exercise in complexity management, and the Agile approach is fundamentally a very useful way of conceptualizing how to manage complexity at a very high level of abstraction.
But as practiced, I've soured on it quite a lot. The ideal is... ahem... ideal, but what we tend to see is kind of a funhouse mirror version of it that, at best, isn't helping. Different flavors of Agile are better (Kanban) or worse (Scrum) about this, but it affects all to one degree or another.