스크럼 마스터와 애자일 코치 그리고 애자일 에반젤리스트(evangelist)는 허갈릴 수 있는 용어이다.
보통은 코칭에 대한 범위가 다르다.
일반적으로 아래와 같다고 생각하면 큰 무리가 없다고 생각된다.
스크럼 마스터 < 애자일 코치 <= 애자일 에반젤리스트
여기서 애자일 코치와 에반젤리스트를 동급으로까지 보는 이유는,, 생각보다 명확하게 나눠진 것이 많지 않으며 애자일 코치 이면서 에반젤리스트로도 충분히 활동할 수 있다고 생각 되기 때문이다. 물론 스케일은 달라질 수 있다.
+
There is nothing terribly official about these terms except that Scrum Master is well defined in the Scrum Guide
Scrum Master
The role as defined in the Scrum Guide. In summary, the Scrum Master:
- Acts as a servant leader to the Scrum Team and Organization, helping them to adopt and get better at Scrum.
- Ensures impediments to Scrum Team delivery of high value software are removed.
- Ensures that the Scrum Team adheres to the Scrum principles, values, roles, rules, and practices.
- Helps Product Owners and Development Team members play their Scrum role, but otherwise does not in any way control or strongly influence how the software is developed and delivered.
A Scrum Master brings value to an organization in these ways:
- A good Scrum Master helps the org adopt and progress towards good Scrum in a feasible way.
- A good Scrum Master helps the Scrum Team deliver higher quality, higher value software faster, by maximizing the benefits received from Scrum.
Scrum Coach
One who can effectively teach and coach all roles as defined in the Scrum Guide(SM, PO, Dev, org). Ideally, IMO, the Scrum Coach will have actual past experience playing all three of the main roles(or very similar roles) somewhere in their background. Another very important trait of a Scrum Coach is experience coaching in a variety of organizational settings. In this way, the Scrum Coach brings best practices about Scrum adoption to the organization. No certification is required to do this, though certified coaches and trainers are usually better than non certified ones. Typically, a Scrum Coach will have bill rates that are 50-100% higher per hour than a Scrum Master, but they also deliver about 400+% more value via their vast coaching experiences across multiple organizations and contexts. Ideally, a Scrum Coach is responsible for taking the Scrum Maturity of one or more Scrum teams to a significantly higher level.
A Scrum Coach brings value to an organization in these ways:
- Utilizing broader experiences and adoption best practices, the Scrum Coach helps the organization and (often multiple) Scrum Teams adopt and progress towards good Scrum in a feasible way.
- A Scrum Coach progresses an organization’s Scrum Maturity much faster and more efficiently than someone with more limited experiences or someone who is playing solely a Scrum Master role.
- Helps (often multiple) Scrum Teams deliver higher quality, higher value software faster, by maximizing the benefits received from Scrum.
Agile Coach vs. Scrum Master
Organizations switching from waterfall to Agile are often confronted with the question:
“What is the difference between an Agile Coach and Scrum Master?”
When they inquire and are looking for a simple answer, things often get more complicated because it raises a discussion about their needs and goals. Here is why:
“Scrum Masters could coach and Agile Coaches can act out the role of a Scrum Master.”
Let’s take a closer look behind the scenes and check out some very important differences. Should we start with the Scrum Master first?
Scrum Masters own the process of the team they are working with. Please note, that I am using singular for the team, as Scrum Masters work commonly with one team, very occasionally with two in parallel. Because Scrum Masters serving more than two teams at once, are commonly much less effective for the teams. The point I am making is that Scrum Masters are closely tied to “a” Scrum process for a specific team, project and organization. Their goal is to mature the process of that team so that the team and indirectly the project can be successful. They will facilitate the Scrum events (planning, daily, review and retro), make progress transparent and help the team to improve through frequent inspection & adaptation. A good chunk of time as a Scrum Master is spent on removing impediments emerging in day to day activities. Yes, technically we could argue that the Scrum Master “coaches” the team but in reality this role is dedicated to “hands-on” Scrum execution. Therefore, Scrum Masters are usually added to a project long-term, ideally for the duration of the project.
The Agile Coach on the other side takes a slightly different angle and view towards an agile project. Agile coaches have a toolkit, a repertoire of techniques and patterns that can push the client forward. Agile coaches often work with Scrum Masters, Product owners, executives, PMO’s and have a much broader zone of impact compared to the Scrum Master. Although agile coaches should have been a successful Scrum Master before, I don’t see it as a career path or hierarchy, these are simply different jobs. Agile coaches can help with transformation, introducing best practices especially useful for larger enterprises. Agile coaches can help traditional project manager shifting towards a role of Scrum Master, or they can act out the role for a short period of time to showcase the role in action. The big words summarizing the difference are “knowledge-transfer” and “enablement”.
Now, you might ask yourself why it would be a good idea to staff a Scrum Master full-time? There are numerous reasons, but that is whole new topic for a separate post.
출처 : https://scrumcrazy.wordpress.com/2011/08/12/scrum-master-vs-scrum-coach-whats-the-difference/