Scrum Master’s Resume To Steer Away From

October 27, 2024October 21, 2024 by Gene

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

Additional References:

Supplementary References (to help you succeed in the role of a scrum master):

Leave a Comment Cancel reply

Dealing with Spill-over Items September 3, 2024
Introduction Spill-over or carryover items are common in many teams. Unfortunately. Focusing on avoiding spill-over can have a positive impact on the team and team dynamics. This article provides insights into what spill-over is, why it’s important, how to prevent it, and what not to do to avoid it, along with strategies for measurement and […]
basvodde
The Rise Of The Product Developers - Part II, Critical Thinking July 20, 2023
In the first part of the Rise of Product Developers series, we explored how Product Developers focus on the domain and users’ problems to build a product. The true value developers bring lies in their critical assessment of what and how they’re building. This approach has always been essential, but it’s become more clear now […]
terry
The Rise Of The Product Developers - Part I, Beyond User Needs March 6, 2023
Inspired by my colleague Bas Vodde’s recent conference talk, I’m embarking on a series about The Rise of the Product Developers. This first piece will focus on how Product Developers can adopt a strategic approach to user requirements. Product Developers build products by understanding the domain and customer problems. Product Developers are not simply coders […]
terry
The Fractal Within a Sprint of Large-Scale Scrum March 13, 2022
A fractal is a structure in which, when you look closer, you will discover self-similarity at different scales. (wikipedia). Zoom In and Out Scrum Fix The Empirical Process Control In Picture A, you can find a typical representation of a Sprint in Scrum, which is, perhaps, a misunderstanding of both iterative development and empirical process. […]
terry