Professional Scrum is the disciplined expression of Scrum guided by empiricism, technical excellence, and continuous delivery of value. It transcends frameworks and rituals, focusing instead on how individuals, teams, and organisations choose to work, with intent, professionalism, and accountability.
At its core, Professional Scrum reflects a philosophy: transparency is not a ceremony, Done is not a suggestion, and empiricism is not optional. This philosophy demands that Product Owners act as strategists, Scrum Masters as agents of change, and Developers as disciplined engineers. It embraces complexity not as a challenge to control, but as a condition to respond to, by learning fast, delivering often, and improving always.
Professional Scrum is not a template. It is how you bring humanity, responsibility, and rigour to complex product delivery. It’s not just doing Scrum. It’s doing it professionally.
The strongest work on Professional Scrum — ranked by substance, not recency. How this is ranked
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 …
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 …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results
Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Scrum Teams don’t set the bar for quality, they meet it
Scrum Teams must consistently meet a clear, non-negotiable Definition of Done to ensure quality, manage risk, and prevent technical debt in …
Definition of Done - Objective vs Subjective
Explains the difference between subjective goals and the objective Definition of Done in Scrum, highlighting how clear, measurable criteria …
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 …
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 …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
Delivery is the only Measure of Progress in Scrum
Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …
The Scrum Master is accountable for Delivery
Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint …
Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery
Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …
Stop Paying the Hidden Costs of Weak Delivery: Why a Strong Definition of Done Transforms Your Team’s Results
Stop paying the hidden costs of weak delivery. Discover how a strong, shared definition of done builds trust, quality, and real agility in …
Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win
Unlock your team's true potential, discover why a powerful definition of done drives real business impact, customer value, and lasting …
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 …
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 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.
Why the Concept of a "Junior Scrum Master" is a Misguided Myth
Explains why the Scrum Master role requires experience and competence, debunking the myth of a "junior" Scrum Master and highlighting the …
Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy
Explains how identifying and validating unrealised value, understanding user needs, and rapid feedback loops can enhance product development …
Unpacking the Scrum Master Role: Moving Beyond Misconceptions to True Accountability
Explores common misconceptions about Scrum Masters, clarifies their true accountabilities, and highlights the importance of principles, …
The Scrum Guide (February 2010)
170 resources, newest first
The Truth About Newbie vs Professional Scrum Masters: Bridging the Experience Gap
Explores the real differences between new and experienced Scrum Masters, challenging common myths and highlighting the importance of …
Can organisations run an Applying Professional Scrum workshop? How would that help them?
Running an Applying Professional Scrum workshop helps organisations build agile skills, improve teamwork, and adopt Scrum practices through …
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 the most common Aha moment people have in a scrum course?
Most people in scrum courses realise the true value of empiricism and purpose behind scrum’s events and artefacts, shifting from rote …
If you could teach just one thing about Scrum, what would it be?
The most important aspect of Scrum is empiricism, using transparency, inspection, and adaptation to navigate complexity and drive effective …
What is the hardest part of working with a brand-new scrum team?
The biggest challenge with new scrum teams is overcoming misconceptions about scrum and shifting focus from process mechanics to core agile …
How much of an impact can a strong, skilled product owner have?
A skilled product owner drives teams to build valuable solutions, anticipate customer needs, and deliver features that create real business …
What will you learn on the professional scrum master course?
Gain practical skills and deep understanding of the scrum master role, scrum theory, empiricism, team dynamics, and delivering value in …
How does the APS course help people apply scrum effectively?
Explains how the APS course uses practical exercises and simulations to help people understand, apply, and improve scrum practices in …
Embrace the Chaos: Transforming Scrum Learning Through Experience and Minecraft
Discover how hands-on Scrum training using Minecraft helps learners experience project chaos, apply agile principles, and gain practical …
Unlocking Scrum Success: A Comprehensive Guide to Values, Roles, Artifacts, and Events
Explains Scrum’s core values, roles, artifacts, and events, highlighting how they support teamwork, transparency, and adaptability in …
Unlocking Success: How the Professional Scrum Product Owner Course Transforms Your Agile Journey
Learn how the Professional Scrum Product Owner course builds agile skills, practical product management, and ongoing support for effective …
Mastering the Art of Scaling Scrum: Insights from the Scaled Professional Scrum Course
Learn practical strategies for overcoming common challenges in scaling Scrum, based on hands-on insights from the Scaled Professional Scrum …
Unlocking Your Potential: Transformative Training for Aspiring Scrum Masters
Comprehensive Scrum Master training offering interactive workshops, practical activities, community support, and assessment to build Agile …
Hiring a Professional Product Owner
Explains the key accountabilities, skills, and behaviours required for a Scrum Product Owner, including hiring trends, role requirements, …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
Sprint Goal is an Immediate Tactical Goal
Explains how the Sprint Goal serves as an immediate tactical objective in Scrum, guiding teams toward strategic Product Goals and maximising …
Story Points & Velocity are a sign of an unsuccessful team
Explains why relying on story points and velocity signals team immaturity in Scrum, and highlights better ways to build confidence and …
If your backlog is not refined then you are doing it wrong
Explains why regular backlog refinement is essential in Scrum, how to make backlog items ready for Sprint Planning, and ways to measure …
Getting started with a Definition of Done (DoD)
Explains how to create, apply, and improve a Definition of Done (DoD) in Scrum to ensure software quality, transparency, and consistent …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
The Sprint Goal is a commitment for the Sprint Backlog
Explains how the Sprint Goal guides Scrum teams by providing a clear, shared objective for each Sprint, ensuring focus, transparency, and …
The Product Goal is a commitment for the Product Backlog
Defines the Product Goal as a clear, measurable objective in the Product Backlog that guides Scrum Teams, ensuring focus, transparency, and …
Update to the Scrum Guide on the 25th Anniversary of the Scrum Framework
Summarises key changes in the 2020 Scrum Guide, including simplified language, self-managing teams, and new commitments for goals, backlog, …
I do continuous deliver, why should I Sprint?
Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and …
The fallacy of the rejected backlog item
Explains why rejecting individual backlog items at Sprint Review is a misconception, highlighting Scrum’s focus on learning, collaboration, …
Delivering Live Virtual Classes in Microsoft Teams and Mural
Guidance on running live virtual Scrum classes using Microsoft Teams and Mural, focusing on tech setup, safe collaboration, self-organising …
Mastering Scrum: Key Insights on Definition of Done, Spikes, and Managing Ad Hoc Work
Explains key Scrum concepts: distinguishing Definition of Done from acceptance criteria, using spikes vs. refinement, and strategies for …
Can the Definition of Done change per Sprint?
The Definition of Done can evolve to improve quality but should not be weakened or vary per backlog item. Consistency ensures transparency …
How do you handle conflict in a Scrum Team?
Guidance on resolving conflict in Scrum Teams, including facilitation techniques, escalation steps, and the Scrum Master's role in fostering …