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
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
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 …
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, …
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 …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
Hiring a Professional Product Owner
A reusable Product Owner job specification covering product leadership, decision authority, customer outcomes and modern product management, …
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 …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
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 …
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 …
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, …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
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 …
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 …
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 …
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 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 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 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 …
The Scrum Guide (February 2010)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …
Nexus Guide
Explains the Nexus framework for scaling Scrum with multiple teams, detailing roles, events, and artefacts to coordinate product delivery …
171 resources, newest first
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 …
In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?
Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and …
Should the Scrum Master always remove impediments?
Explains when a Scrum Master should remove impediments, focusing on team self-sufficiency, true impediments, and supporting team growth …
Are technical skills required to be a Scrum Master?
Technical skills are not required to be a Scrum Master, but understanding technical, business, and organisational contexts helps Scrum …
Work can flow across the Sprint boundary
Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …
Professional Scrum is for everyone in your organisation
Explains how involving everyone in Professional Scrum training fosters organisational agility, breaks down silos, and empowers teams to …
Professional Scrum Training for the Ghana Police Service
Professional Scrum training introduced Ghana Police officers to Agile methods, using hands-on sprints to support organisational change and …
Big Scrum: All you need and not enough
Explores how to scale Scrum effectively by applying agile values, fostering professional teams, and adapting processes to fit unique …
Big Scrum: Are you doing mechanical Scrum
Explores the difference between mechanical and Professional Scrum, highlighting the importance of values, principles, and technical …
My journey into Professional Scrum
Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges …
Professional Scrum Foundations in Alameda, California
Covers a two-day, hands-on Scrum.org course in Alameda, teaching Scrum principles, teamwork, and practical software delivery for all roles …
What's in a burndown?
Explains burndown charts in Scrum, their purpose, common issues, and compares tracking by hours, story points, and acceptance tests to …
Can you really commit to delivering work?
Explores why Scrum shifted from "commitment" to "forecasting" work delivery, highlighting the risks of overpromising and the benefits of …
Are you doing Scrum? Really?
Explains recent changes to Scrum aimed at reducing rigidity, clarifying core practices, and providing a checklist to help teams assess if …
Product Owners are not a myth
Explains the Product Owner role in Scrum, common challenges with proxies, and how support teams like Business Analysts can help manage large …
You are doing Scrum but the Scrum Master tells the team what to do!
Explains why Scrum Masters should not direct teams, emphasising self-organisation, shared responsibility, and the importance of team …
Coffee Talk: Introduction to Scrum - webcast event this Friday!
Learn the basics of Scrum, including its key roles and processes, with practical tips for adoption. Ideal for those new to agile or seeking …
My first Scrum team in the wild
A real-world account of guiding a new Scrum team through their first sprint, covering estimation, story points, sprint planning, and …
Professional Scrum Developer (.NET) Training in London
Intensive five-day course for software developers covering Scrum, Visual Studio 2010, .NET, and Agile practices through hands-on team …
Adventures in Scrum: Lesson 1 – The failed Sprint
Explores common pitfalls in early Scrum adoption, highlighting why full team involvement in sprint planning is crucial and lessons learned …
The Scrum Guide (February 2010)
A clear summary of Scrum’s framework, roles, events, artefacts, and values, explaining how teams use Scrum to deliver value and adapt to …