As I reflect on the journey of Scrum Masters and their progression through the Professional Scrum Master (PSM) certifications, I can’t help but notice a troubling trend: many Scrum Masters never advance beyond the PSM1 level. This observation leads me to a crucial question: why is that?
From my experience, the answer often boils down to a lack of genuine interest. Many individuals enter the certification process not out of a desire to deepen their understanding of Scrum or to enhance their skills, but rather because they’ve been instructed to do so by their organisations. They approach the training with a singular focus on obtaining the certificate, often asking questions like, “What happens with the exam?” or “How do I get the certificate?” This mindset reveals a fundamental disconnect; they are not truly invested in becoming better Scrum Masters.
The Importance of Passion in Professional Growth
I once came across a thought-provoking blog post that began with a striking statement: “If you’re reading this, you’re already in the top 10% of all software engineers.” The essence of this statement is that very few people are genuinely passionate about their work. Those who are willing to invest their time outside of work, whether by reading, listening to podcasts, or engaging with their professional community, are the ones who truly excel.
Here’s what I’ve observed about those who progress to PSM2 and PSM3:
- They Care: These individuals are not just clocking in and out. They are invested in their craft and the success of their teams.
- They Seek Knowledge: They actively pursue learning opportunities, whether through books, podcasts, or discussions with peers.
- They Practice: Just like violinists and martial artists, they understand that mastery comes from practice. They dedicate time to refine their skills and explore new methodologies.
The Role of the Scrum Master
As Scrum Masters, our primary accountability lies in enhancing the effectiveness of our teams and generating value within our organisations. To fulfil this role effectively, we must continuously learn and adapt. Here are some strategies I recommend for those looking to deepen their Scrum Master skills:
- Engage with Content: Make it a habit to read agile literature and follow thought leaders in the field. This will not only broaden your understanding but also inspire new ideas.
- Listen to Podcasts: During your commute or downtime, opt for podcasts that discuss agile practices, Scrum methodologies, and team dynamics. This can be a great way to absorb knowledge while multitasking.
- Network with Peers: Join communities or forums where you can discuss challenges and share insights with fellow Scrum Masters. Engaging with others can provide fresh perspectives and solutions.
Conclusion
In conclusion, the journey from PSM1 to PSM2 and PSM3 is not merely about obtaining a certificate; it’s about a commitment to personal and professional growth. If you’re serious about your role as a Scrum Master, take the time to invest in your development. Remember, the best Scrum Masters are those who are passionate about their craft and dedicated to helping their teams succeed.
If you found this post insightful, I encourage you to like, follow, and subscribe for more content on agile, Scrum, and DevOps. I always welcome comments and discussions, so feel free to reach out or book a coffee chat with me through Naked Agility. Let’s continue to learn and grow together!
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Why Pursuing Agile Certifications is Your Key to Career Advancement
Explains how Agile certifications validate knowledge, support continuous learning, and help employers assess candidates, while emphasising …
Transform Your Scrum Master Journey: Key Insights from the Advanced PSM Course
Discover how the Advanced PSM course helps Scrum Masters shift from admin tasks to empowering teams, supporting Product Owners, and tackling …
What is your best advice for becoming a Scrum Master outside software engineering?
Practical guidance on becoming a Scrum Master outside software, covering certification, skill development, validated learning, and applying …
Redefining the Scrum Master: From Misconceptions to Empowering Leadership
Explores common misconceptions about the Scrum Master role, highlighting the shift from tool admin to empowering leader who fosters team …
Unlocking the Scrum Master's Potential: Embracing Broader Responsibilities for Agile Success
Explores how Scrum Masters can expand their impact by embracing wider organisational responsibilities, challenging outdated practices, and …
A two-day Scrum Master certification doesn’t make you a Scrum Master
Practical experience is essential for effective Scrum Masters; certification alone is insufficient. True expertise comes from guiding teams, …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.