Jan Krchňák

In the first part of our series, we covered why you should be interested in Agile maturity in your teams or organizations and how to look at it. In the next installment of our series, we’ll focus on “measuring Agile mechanics”.

What is the right development methodology for your organization? That’s a question that the Cynefin framework can help you with. It argues that to choose the right solution to a problem, you first need to […]

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.