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
Challenging Misconceptions About Behaviour in Agile Teams
Explores common misconceptions about Agile teams, clarifying that true agility demands discipline, planning, and professionalism, not chaos …
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 …
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 …
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 …
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 Crucial Role of Competence: How Knowledgeable Scrum Masters Drive Team Success
Scrum Masters with deep knowledge and competence enable teams to deliver better products, drive business outcomes, and foster real …
The Competence Crisis in Scrum Master Roles: A Call for Excellence
Many Scrum Masters lack essential skills and experience, leading to poor agile outcomes. True competence requires deep knowledge, practical …
Evidence-Based Management: The Four Key Value Areas in Scrum
Explains Scrum’s four key value areas, current value, unrealised value, ability to innovate, and time to market, for data-driven product and …
Mastering Evidence-Based Management in Agile: Inform, Don’t Control
Explains how to use data in Agile management to guide decisions and behaviours, focusing on informed outcomes without letting metrics …
Why Most Scrum Masters Are Failing and What They Should Know
Many Scrum Masters lack core Scrum knowledge and technical skills, leading to poor team support. Learn key competencies needed for …
Product Ownership vs. Product Management: Busting the Myth That They're Separate Roles
Explains why product ownership and product management are deeply connected in Scrum, clarifying their roles, focus on value delivery, and …
Debunking the Top 5 Myths About Scrum: Unlocking Agile Success in Your Organisation
Explores and corrects common misconceptions about Scrum, clarifying its true principles, events, planning, and governance to help teams …
Maximise Your Scrum Process: Leveraging Azure DevOps for Agile Success
Learn how to customise Azure DevOps to support Scrum teams, manage backlogs, plan sprints, and improve agile workflows with practical setup …
Pragmatism crushes Dogma in the wild
Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …
Unlocking Business Value: The Power of Evidence-Based Management for Effective Leadership
Explains how evidence-based management uses data-driven decisions and tailored metrics to boost business value, leadership effectiveness, …
The Importance of Evaluating Direction: Are You Heading the Right Way?
Learn why regularly evaluating your direction is vital for developers, product owners, and organisations to ensure goals, features, and …
Say-Do Metrics: Avoiding Agile Banditry in Your Organization
Explains the risks of using say-do metrics in Agile, highlighting how they encourage vanity metrics, harm psychological safety, and shift …
Ditching the Myth of Special Sprints: Embrace True Agile Practices for Usable Products
Explains why relying on special Sprints undermines Agile, and advocates for continuous improvement, accountability, and delivering usable …
Mastering Product Backlog Management: Essential Skills for Product Owners
Learn the core skills and best practices for effective product backlog management, including risk, value, sizing, learning, and refinement …
Mastering Scrum: Essential Insights for New Teams from a Scrum Master's Journey
Guidance for new Scrum teams on building strong foundations, embracing empiricism, Scrum values, continuous learning, and the Scrum Master's …
Understanding the True Role of a Scrum Master
Explains the true responsibilities of a Scrum Master, how to maximise team effectiveness, teach Scrum principles, and address organisational …
Why Every Scrum Master Needs an Immersive Training Experience
Immersive training helps experienced Scrum Masters deepen practical skills, boost team effectiveness, and develop leadership through …
Unlocking the Power of Double-Loop Learning: Transform Your Scrum Master Journey with Immersive Training
Explore how immersive, double-loop learning in Professional Scrum Master training helps Scrum Masters apply theory, reflect, and collaborate …
Unlocking Success in Agile: Why Your Definition of Done is Essential for Quality Delivery
Explains why a clear Definition of Done is vital in Agile and Scrum for quality delivery, transparency, and risk mitigation, with tips for …