Competence is the foundation for professional effectiveness. It requires individuals and organisations to actively develop, demonstrate, and apply the skills, knowledge, and judgement necessary to deliver quality outcomes. Without competence, no framework, process, or tool can succeed.
Competence as a first principle demands continuous learning, deliberate practice, and a commitment to mastery. It is not assumed. It must be earned, inspected, and adapted over time. It’s what separates performative activity from real progress.
If you can’t execute with competence, you’re gambling with quality, trust, and value delivery. Every decision, every action, every commitment must be grounded in the capability to follow through with professionalism and expertise.
The strongest work on Competence — ranked by substance, not recency. How this is ranked
Scrum Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
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, …
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 Crucible of Learning: Transforming Organizational Effectiveness Through DevOps
Explores how DevOps transformation, refactoring, and ownership reduce technical debt, streamline development, and boost efficiency, team …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …
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 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 …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
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, …
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 …
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 …
You are doing it wrong if you are not using test first
Explains how adopting test-first practices in software development improves quality, reduces bugs, and enables confident continuous delivery …
Professional Scrum teams build software that works
Professional Scrum Teams prioritise software quality, accountability, and continuous improvement, ensuring each release is reliable, …
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 …
The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps
Explores how DevOps transformation, refactoring, and ownership reduce technical debt, streamline development, and boost efficiency, team …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …
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 …
Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration
Explores how competence, collaboration, and agile philosophies drive high-performance software delivery, focusing on business value, …
Cultivating a Culture of Engineering Excellence: The Essential Role of Technical Leadership
Explores how technical leadership shapes a culture of engineering excellence through clear standards, continuous learning, collaboration, …
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 Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI
Incompetent Scrum Masters reduce team performance and ROI by lacking key skills. Learn how to measure their impact using innovation, usage, …
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 …
70 resources, newest first
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 …
You can’t deliver change through memos
Change succeeds when everyone understands and engages with it. Broad Scrum training empowers all roles to identify blockers and drive real, …
David thought he already knew Scrum
Discover why experienced Scrum practitioners often misunderstand core principles, and how revisiting Scrum fundamentals restores clarity, …
A certification proves you’ve passed a test
Certifications show test-passing ability but don’t prove real-world product skills. Experience, judgement, and stakeholder influence matter …
Executives want predictability
Lack of a clear, enforced Definition of Done leads to hidden risks, unreliable forecasts, and eroded trust in delivery, undermining …
Too many Scrum Masters believe they don’t need technical skills
Highlights the importance of technical knowledge for Scrum Masters, arguing that understanding team-specific skills is essential to …
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 Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
Realistic Expectations When Hiring Junior Scrum Masters
Understand the risks of hiring inexperienced junior Scrum Masters, including higher costs, team issues, and project delays, versus investing …
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, …
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 …
Key Skills Scrum Masters Need: Technical, Business, Organisational
Scrum Masters need technical, business, and organisational skills to guide teams, remove obstacles, drive value, and lead effective agile …
The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master
Hiring an unqualified Scrum Master limits team growth, reduces agility, and hinders value delivery. Effective Scrum Masters drive change, …
Would you hire a Junior CISO? A Junior Financial Director
Scrum Masters require proven expertise, not entry-level skills. Hiring juniors in this role risks team performance and agile success; …
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 …
Hiring a Scrum Master is hard
Finding a skilled Scrum Master is challenging; true effectiveness requires deep Scrum knowledge, coaching ability, and alignment with your …
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 …
Building a High-Performance Delivery Engine: Unlocking Success Through Competence and Collaboration
Explores how competence, collaboration, and agile philosophies drive high-performance software delivery, focusing on business value, …
Cultivating a Culture of Engineering Excellence: The Essential Role of Technical Leadership
Explores how technical leadership shapes a culture of engineering excellence through clear standards, continuous learning, collaboration, …
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 Problem with Incompetent Scrum Masters: Why Lack of Skills in Team Context Results in Poor ROI
Incompetent Scrum Masters reduce team performance and ROI by lacking key skills. Learn how to measure their impact using innovation, usage, …
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 …
The Importance of Competence in Organizations: Building a Culture of Learning and Growth
Explores how fostering competence, continuous learning, and well-being in organisations leads to happier teams, better products, and …
Where Agile Went Wrong: Understanding the Competence Crisis
Explores how early assumptions about competence led to Agile’s current skills gap, highlighting the need for continuous learning, better …
Focusing Beyond "Agile": Building True Capability in Organizations
Explores why building organisational capability, competence, and continuous learning is more effective than focusing solely on Agile roles, …
Agile is Not New: A Journey Back to the Basics
Explores Agile’s historical roots, the loss of human connection in business, the impact of competence gaps, and why a return to core Agile …
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 …
The Crucible of Learning: Transforming Organizational Effectiveness Through DevOps
Explores how DevOps transformation, refactoring, and ownership reduce technical debt, streamline development, and boost efficiency, team …
The Power of Technical Excellence in Agile Development
Explores how technical excellence in Agile development reduces risk, prevents technical debt, and boosts product quality and delivery speed …