Kentico

What is DevOps? How to explain benefits to the entire organization? How to deal with company culture? It’s Friday, May 19th. We are sitting at the Rome – Ciampino airport with Jan waiting for our […]

Agility has become popular across many industries. In IT where it has originated it is de facto standard. However, we also experience many Banks claiming they run more or less successfully an Agile transformation. Let’s […]

In recent years, I’ve noticed a conflicting perception of the role of Scrum Master (SM) or Agile Coach (AC, for simplicity, I won’t differentiate between these roles further in this article) in companies and the agile community. On the one hand, it says that it is a necessary role for operating in an agile/lean way, for pushing change and directing the company culture. On the other hand, there are business ungraspability of the role, the difficulty of defining its meaning, benefits, goals and their measurability, and the related fact that it is one of the first roles to go when “saving” is needed. I understand both sides and in this article I will try to offer a view on how to grasp this role so that the benefits stand out and at the same time it makes sense from a business perspective.