Kentico

Have you ever noticed that we seek for complex solutions and yet simple things work incredible well? This short article describes one such a practice we call Show & Tell. I guess you heard of Show […]

You know how it goes. There is a group of coworkers round the table and they report one after another project status to their manager. Everyone should be interested in work of others but the […]

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.