Highlights the importance of technical knowledge for Scrum Masters, arguing that understanding team-specific skills is essential to effectively support and enable their teams.
Too many Scrum Masters believe they don’t need technical skills. The Scrum Guide doesn’t explicitly say they do—but let’s be real.
If a Scrum Team is building software, a Scrum Master who doesn’t understand Test-Driven Development, Continuous Delivery, and DevOps is out of their depth. If the team is in finance, the Scrum Master should grasp financial modelling and compliance. If it’s an industrial design team, they should understand prototyping and material constraints.
Scrum Masters don’t do the work, but they enable the work. And how can you enable what you don’t understand?
Being a great Scrum Master isn’t about certification. It’s about mastery—of the technical, business, and organisational realities your team faces.
Are we setting Scrum Masters up for success, or are we pushing them into roles where they lack the mastery to make a real impact?
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Schlumberger
SuperControl
Bistech
Cognizant Microsoft Business Group (MBG)
Healthgrades
Kongsberg Maritime
Illumina
Slaughter and May
Flowmaster (a Mentor Graphics Company)
Capita Secure Information Solutions Ltd
CR2
Trayport
Lockheed Martin
Alignment Healthcare
Boxit Document Solutions
Epic Games
NIT A/S
Xceptor - Process and Data Automation
Washington Department of Enterprise Services
New Hampshire Supreme Court
Royal Air Force
Ghana Police Service
Nottingham County Council
Department of Work and Pensions (UK)
DFDS
Cognizant Microsoft Business Group (MBG)
Bistech
Workday
YearUp.org
Qualco