The Agile in software projects changed the way that professionals and organizations are analyzing, measuring and transforming teams. But sometimes the teams are not mature enough to self-manage conflicts that are about to happen or even detect issues in the process that will cause performance problems in the future. Thus, companies are increasingly searching for professionals focused on transforming the team and the process, seeking to evolve the organization as a whole.
Many roles have been created from this need. Some of them you have certainly heard or even have in your team, such as Scrum Master and Project Manager. Others are relatively new, like the Agile Coach.
What is an Agile Coach?
Agile Coach is a transformation agent whose purpose is to evolve people, the team and the organization in order to reconcile four areas:
- Technical domain: related to all the technical and architectural part of the team;
- Business domain: which involves operational strategies, process and innovation;
- Team domain: related to the team itself, such as facilitation and leadership;
- Personal domain: individual, such as career development and internal problems.
Agile Coach x Scrum Master
What are the differences between an Agile Coach and a Scrum Master? The Scrum Master is focused on making the process to follow all rules of the Scrum framework (eg ceremonies, artifacts), always aiming for constant and timely deliveries. And quality, of course.
Agile Coach has the focus of transforming the team, finding and preventing problems. In addition to proposing solutions for them.
Thus, we can conclude that while the Scrum Master has the delivery as its customer and is a reactive agent in the process, Agile Coach works as an active agent, having as its customer the team itself.
This is a briefing of my on going studying about the Agile Coach and how we can act to transform and evolve the environment we are involved with. I'm planning to post practical ways of getting to the improvement of some requirements addressed.