Looking For Your Next Gig? Avoiding Bad Advice About Scrum Master Role.

SCRUM “MINISTER”

This is an anecdotal SM resume. It is fabricated, based on real life examples of what transpires in the world of agile. Consider this as an example of what NOT do in real life, NOT say at an interview, NOT write on a resume and NOT select in a candidate, if you are hiring for the role of a scrum master.

The WHO:
- Scrum Master / Agile Project manager
- Scrum Master / Agile PMO
- Scrum Master / Scrum team manager
- Scrum Master / Agile Delivery Manager
- Scrum Master / Agile Delivery Lead

The WHAT (responsible for):
- “managing” agile-scrum projects
- assigning/removing team members to/from a team
- defining a product
- setting product and/or sprint priorities
- defining sprint goals and commitments
- scheduling/running scrum meetings
- creating/assigning tasks to developers
- proving technical solutions to developers
- ordering technical work during a sprint
- managing/configuring/updating ticket tracking tools
- participating in work estimation
- collecting metrics and generating “agile” status reports
- reporting to management on a team’s progress
- taking responsibility/delivering on a team’s commitments
- coordinating dependencies within and between teams
- coordinating between a product owner and team members
- managing communication between teams/developers and users
- presenting team accomplishments during a sprint review
- providing feedback/evaluating teams’ performance
- doing performance appraisals on individual team members