Happy New Year fellow ScrumD'ers!
Towards a Good Scrum Master Job Description
I've cobbled together(mostly from other sources) a Scrum Master job
description for a client, and I'd be interested in any feedback anyone
has. This position is for an "Experienced Scrum Master" who would be an
SM for 1-2 software development teams of appropriate Scrum team size. My current hope/plan is to get feedback here and then post to my blog/web site in the near future.
Feel free to use this job description as you please, and no need for
attribution. Cut, paste, do whatever you want with it. Just don't mangle
it and then say it was from ScrumCrazy.com
. Also, use at your own risk
-- no warranties, no promises, etc.Feedback welcome and encouraged!
- Strongly serving and supporting the Product Owner and Development Team
in their quest to do everything possible to delight customers
- Guiding the Scrum Team and organization on how to use Agile/Scrum practices and values to delight customers
- Guiding the Development team on how to get the most of out self organization
- Guiding the Development team on self-organizing to fill in the intentional gaps left in the Agile/Scrum frameworks
- Assessing the Scrum Maturity of the team and organization and coaching
the team to higher levels of maturity, at a pace that is sustainable
and comfortable for the team and organization
- Removing impediments or guiding the team to remove impediments by finding the right personnel to remove the impediment.
- Building a trusting and safe environment where problems can be raised
without fear of blame, retribution, or being judged, with an emphasis of
healing and problem solving.
- Facilitating getting the work done without coercion, assigning, or dictating the work.
- Facilitating discussion, decision making, and conflict resolution
- Assisting with internal and external communication, improving transparency, and radiating information
- Supporting and educating the Product Owner, especially with respect to grooming and maintaining the product backlog.
- Providing all support to the team using a servant leadership
style whenever possible, and leading by example. This person should
personify Scrum and Agile.
- First level Scrum Master certification (PSM I, CSM)
- Experience playing the Scrum Master role for at least one year for a software development team
- Good skills and knowledge of servant leadership, facilitation,
situational awareness, conflict resolution, continual improvement,
empowerment, and increasing transparency
- Knowledge of numerous well documented patterns and techniques for
filling in the intentional gaps left in the Scrum approach(example:
numerous Burndown techniques, numerous Retrospective formats, handling
- The ability to distinguish between what "is Scrum" what is "not Scrum"
Preferred Skills/Experience (Any of these is a plus)
- Second level Scrum Master certification (PSM II, CSP)
- Experience playing the Scrum Master role for at least two years for a software development team.
- Experience being on multiple Scrum teams in a variety of different
contexts (different team sizes, different organizations, different
cultures, co-located vs. distributed, etc)
- Knowledge of other approaches discussed in the Agile space: XP, Kanban, Crystal, FDD, etc
- Knowledge and/or experience with widely successful Agile techniques:
User Stories, ATDD, TDD, Continuous Integration, Continuous Testing,
Pairing, Automated Testing, Agile Games
- Applicable knowledge of the technologies used by the team
- Experience applying a wide variety of well documented patterns and
techniques for filling in the intentional gaps left in the Scrum
approach(example: numerous Burndown techniques, numerous Retrospective
formats, handling bugs,etc)
- Previous experience as a team lead
- Excellent communication and mentoring skills
</end job description>
Some other things you(the job poster) might want to fill in:
- Required education level
- Required software product development experience (I don't recommend
picking a particular development role -- just general software
- Any other things that you feel are important to your project, company, or team culture
Professional Scrum Trainer