Ethos is not what you say you value, it’s what your system proves you believe.
Everything on this site reflects a consistent ethos: value delivery over activity, accountability over role-playing, system evolution over compliance, evidence over opinion. This ethos drives how we apply Scrum as a social technology, how we use Kanban as an observability pattern, and how we treat DevOps as a delivery enabler, not a toolchain.
Your principles emerge from ethos. So do your working agreements, your feedback loops, your definition of done, your deployment cadence, your response to failure, and your tolerance for nonsense. You can’t build a sustainable delivery system without it.
Ethos is what keeps your teams from falling back into habits that feel comfortable but deliver nothing. It holds the line when pressure mounts and shortcuts tempt. It’s the difference between agility that lasts and transformations that collapse into ceremony.
This site exists to support that ethos. Every method, recipe, principle, and workshop here is grounded in it. If you don’t share the ethos, the tools won’t work. If you do, the system will evolve, continuously, deliberately, and with integrity.
The strongest work on Ethos — ranked by substance, not recency. How this is ranked
Engineering as a Leadership System
Session recording from The Future of Work in Scotland. Why the frameworks your teams adopt cannot overcome the operating model your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Detecting agile theatre with real delivery signals
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 …
How My Father's Business Reverted to the Mean
My father died eight years ago today. In 1980 a leadership team's golf retreat left him holding a ten-year lease on a Glasgow shopfront, so …
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 …
What is Taylorism, and why Waterfall is just the tip of the iceberg!
Explores how Taylorism shaped modern management, leading to rigid hierarchies, bureaucracy, and dehumanising work practices that persist …
Rethinking Continuous Delivery: Why Best Practices Don't Exist in Complex Environments
Explores why fixed best practices don't suit complex continuous delivery, highlighting adaptive approaches like audience-based delivery, …
Special Sprints: Agile Banditry or Risk Management?
Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
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 …
How My Father's Business Reverted to the Mean
My father died eight years ago today. In 1980 a leadership team's golf retreat left him holding a ten-year lease on a Glasgow shopfront, so …
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 …
Stop normalizing unprofessional behaviour in the name of agility
Highlights the importance of professionalism in agile teams, warning against excusing unprofessional behaviour as agility and stressing …
What is Taylorism, and why Waterfall is just the tip of the iceberg!
Explores how Taylorism shaped modern management, leading to rigid hierarchies, bureaucracy, and dehumanising work practices that persist …
Many organisations are lured to SAFe by the song of the Sirens
Explores how organisations adopt SAFe for agility but risk rigid bureaucracy, highlighting the need for genuine business evolution over …
Big Scrum: Are you doing mechanical Scrum
Explores the difference between mechanical and Professional Scrum, highlighting the importance of values, principles, and technical …
Engineering as a Leadership System
Session recording from The Future of Work in Scotland. Why the frameworks your teams adopt cannot overcome the operating model your …
Rethinking Continuous Delivery: Why Best Practices Don't Exist in Complex Environments
Explores why fixed best practices don't suit complex continuous delivery, highlighting adaptive approaches like audience-based delivery, …
Special Sprints: Agile Banditry or Risk Management?
Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …
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.
Is Your Engineering Culture Ready to Scale with Your Technology?
Explores why scaling technology alone isn’t enough, highlighting the need for engineering cultures that support collaboration, DevOps, and …
Balancing Speed and Stability: Why Quality Should Always Come First in Delivery Management
Explores why prioritising quality and stability over speed in delivery management leads to better long-term outcomes, even when facing tight …
Building a culture of Quality
Explores how fostering a culture of quality and engineering excellence across teams leads to better, safer products, highlighting the impact …
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, …
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 …
60 resources, newest first
How My Father's Business Reverted to the Mean
My father died eight years ago today. In 1980 a leadership team's golf retreat left him holding a ten-year lease on a Glasgow shopfront, so …
Engineering as a Leadership System
Session recording from The Future of Work in Scotland. Why the frameworks your teams adopt cannot overcome the operating model your …
Detecting agile theatre with real delivery signals
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 …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
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.
Why Resilience Demands More Than Survival
True organisational resilience means improving technical health, like testing, automation, and architecture, beyond just surviving incidents …
Why Copying Scaled Agile Frameworks Fails in Your Business
Copying scaled agile frameworks fails because each business needs a tailored, evidence-based approach to agility that fits its unique …
When Heathrow went down, they blamed the power supplier
Heathrow’s outage was caused by an over-sensitive disaster recovery system, not a power loss, highlighting the risks of untested resilience …
Everyone has a disaster recovery plan, on paper
Most disaster recovery plans fail in practice due to overlooked dependencies and lack of real-world testing, leaving organisations …
You can not implement Agile or Scrum successfully by decree
Mandating Agile or Scrum fails without cultural change; true agility requires trust, transparency, and a supportive environment, not just …
Companies often say "we-are going Agile!" as if declaring it makes it so
Many companies mistake adopting Agile frameworks for true agility, but real success comes from customising ways of working to respond …
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, …
Is Your Engineering Culture Ready to Scale with Your Technology?
Explores why scaling technology alone isn’t enough, highlighting the need for engineering cultures that support collaboration, DevOps, and …
How Top Scrum Masters Are Selected by Their Teams
Explains how Scrum Masters are naturally chosen by teams based on trust, experience, and leadership, highlighting the importance of peer …
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 …
Balancing Speed and Stability: Why Quality Should Always Come First in Delivery Management
Explores why prioritising quality and stability over speed in delivery management leads to better long-term outcomes, even when facing tight …
Rethinking Continuous Delivery: Why Best Practices Don't Exist in Complex Environments
Explores why fixed best practices don't suit complex continuous delivery, highlighting adaptive approaches like audience-based delivery, …
Building a culture of Quality
Explores how fostering a culture of quality and engineering excellence across teams leads to better, safer products, highlighting the impact …
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, …
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 …
Avoiding the Seven Deadly Sins of Agile: Transform Your Organisation for True Agility
Identifies seven common Agile pitfalls, quick fixes, backlog overload, resource focus, lack of accountability, blame, imitation, and pride, …
Special Sprints: Agile Banditry or Risk Management?
Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …
Overcoming the Ghost of Agile Certifications
Explores the limits of Agile certifications, emphasising real-world experience, continuous learning, and team validation over credentials …
Introduction to Agility’s Ghosts: Shedding Dogma and Embracing Pragmatism
Explores the dangers of dogmatism in Agile, highlighting the need for flexibility, pragmatism, and people-focused adaptation over rigid …
The Power of Humility in Agile: A Core Virtue for Success
Explores how humility strengthens Agile teams by fostering trust, collaboration, openness to feedback, and better decision-making through …
The Power of Kindness in Agile: A Core Virtue for Success
Explores how kindness, empathy, and compassion in Agile foster trust, improve team collaboration, and enhance customer focus for long-term …
The Power of Charity in Agile: How Helping Others Elevates Teams and Organizations
Explores how practising charity, helping others without expecting rewards, strengthens Agile teams, boosts collaboration, and drives …
Embracing Chastity in Agile: Why Taking Your Time is Key to True Transformation
Explores the importance of patience in agile adoption, highlighting inclusive decision-making, stakeholder engagement, and thoughtful …
Breaking the Silence: How to Combat the Hidden Dangers in Agile Teams
Explores the risks of unspoken issues in Agile teams, detailing how silence harms communication, trust, and value delivery, and offers …
The Antichrist of Agile: How Fake Agilists Are Undermining True Innovation
Explores how unqualified Agile practitioners undermine genuine innovation, erode trust, and hinder software teams, stressing the need for …
7 Harbingers of the Agile apocalypse - Chaos
Explores how chaos arises in agile transformations due to unclear vision and poor communication, and offers strategies for restoring …
Conquering Sloth in Agile: 6 Signs Your Team Might Be Stalling
Learn to spot six key signs of sloth in Agile teams, including missed deliveries, ignored feedback, rigid processes, and lack of adaptation, …
7 harbingers of the Agile apocalypse - Judgement
Explores how rigid, judgmental Agile practices stifle creativity and innovation, and advocates for principle-driven, adaptable approaches to …
7 Harbingers of the Agile Apocalypse - Plague
Explores the widespread issue of incompetent Agile coaches and Scrum Masters, its impact on teams and organisations, and practical steps to …
What is the one thing that no Agile team can survive?
Explores how a culture of contempt undermines Agile teams, its causes, impact on morale and productivity, and practical steps leaders can …
7 deadly sins of Agile: Lust
Explores why Agile transformation requires genuine commitment and adaptation, warning against quick fixes and emphasising the need for a …
7 deadly sins of Agile: Envy
Explores how envy leads teams to copy Agile models like Spotify, warns against FOMO-driven adoption, and stresses tailoring Agile practices …
Transforming Agile: How to Shift from Blame to Systemic Solutions for Better Team Dynamics
Explores how shifting from blame to addressing systemic issues and measurement systems can improve team dynamics, collaboration, and agility …
Do you think we are on the slope of enlightenment in Gartner's Hype Cycle?
Explores whether organisations are moving past Agile disillusionment towards true understanding, highlighting the shift from hype to …
Most Common Thing You Hear in a PSM 1 Course?
Explores the common challenge in PSM 1 courses of balancing real-world pressures with maintaining honesty, transparency, and moral integrity …
Hardest Part of Adopting Scrum?
Overcoming the belief in quick fixes is the hardest part of Scrum adoption; true success requires mindset change, continuous learning, and …
Biggest contribution from a Product Owner that you know of
Explores how visionary Product Owners at Microsoft drove Agile transformation, shortened feedback cycles, and reshaped product development …
Unlocking Transformation: Why Embracing Difficult Conversations with Agile Consultants is Key to Success
Explores how open, challenging conversations with agile consultants drive organisational change, foster learning, and support continuous …
Unlocking Trust in Scrum: The Power of Openness and Transparency
Explores how openness and transparency in Scrum foster trust, clear communication, and a supportive team culture, essential for effective …
Why do you prefer agile consulting over agile coaching?
Explains why agile consulting is preferred over coaching, focusing on empowering internal leadership, fostering self-reliant teams, and …
Why is Scrum so easy to understand but incredibly hard to master?
Explores why Scrum is challenging to master, highlighting cultural barriers, the importance of transparency, and the gap between …
Why did you choose the Scrum.Org track rather than the Scrum Alliance track?
Explains choosing Scrum.Org over Scrum Alliance, focusing on values, certification costs, flexibility, community support, and alignment with …
Why did so many of the early agile transformations fail?
Early agile transformations often failed due to top-down decisions, lack of team involvement, and misalignment between leadership and those …