The strongest articles on engineering excellence and technical leadership — 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 …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
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 …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
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 …
The articles that speak most directly to technical leadership — ranked by that classification’s score alone.
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 …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
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 …
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, …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
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 …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
The articles that speak most directly to engineering excellence — ranked by that classification’s score alone.
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
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 …
Testing in Production Maximises Quality and Value
Explains how audience-based deployment and testing in production enable faster feedback, safer rollouts, and higher software quality by …
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 …
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 Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Resilience is Part of the Product, Not an Afterthought
Resilience must be designed into products from the start, not added later. Build systems to detect, contain, and recover from failures, …
420 resources, newest first
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 …
Hiring a Professional Scrum Master
Covers key responsibilities, skills, and requirements for hiring a Scrum Master, including leadership, coaching, facilitation, and fostering …
Scrum is made up of Influencers, Entrepreneurs, and Makers
Explains how Scrum teams rely on three key roles, Influencers, Entrepreneurs, and Makers, to balance leadership, value creation, and …
Become the leader that you were meant to to be
Explores the shift from traditional management to leadership focused on inspiration, effectiveness, and servant leadership, with insights …
All technical debt is a risk to the product and to your business
Technical debt increases risk to products and businesses, leading to hidden costs, reduced quality, and slower delivery. Ignoring it can …
Professional Kanban Trainer for Applying Professional Kanban
Learn about becoming a Professional Kanban Trainer, the Applying Professional Kanban course, certification process, and key Kanban …
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 …
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 …
Evidence-based Management: Gathering the metrics
Explains how to gather key metrics for evidence-based management in software organisations, focusing on value delivery, time to market, and …
There is no place like production
Validating product value requires releasing features to real users in production, gathering feedback, and measuring usage, satisfaction, and …
Product Goal is an Intermediate Strategic Goal
Explains how product goals serve as intermediate strategic goals, guiding agile organisations through uncertainty using experimentation, …
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 …
A better way than staggered iterations for delivery
Explains why staggered iterations harm software delivery, increasing technical debt, and recommends cross-functional teams, test-first, and …
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, …
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 …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
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, …
Online is the new co-located
Explores how advances in technology have redefined co-location, emphasising the importance of video presence for effective online …
What my father taught me about Evidence-based Management (34 years before it was invented!)
Explores how evidence-based management uses data-driven practices to improve organisational agility, value delivery, and decision-making in …
I do continuous deliver, why should I Sprint?
Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and …
Getting started with a modern source control system and DevOps
Learn key practices for adopting modern source control and DevOps, including automation, release pipelines, and team collaboration to …
Evolution not Transformation: This is the Inevitability of change
Change in organisations is a continuous, evolutionary process driven by experimentation and adaptation, not a one-time transformation or …
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, …
Luddites have no place in the modern organisation
Explores how resistance to change and outdated mindsets hinder organisational agility, stressing the need for adaptable, forward-thinking …
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 …
Configuring Microsoft Teams for Live Virtual Training
Step-by-step guide to setting up Microsoft Teams for live virtual training, covering Azure AD, Microsoft 365, guest access, external …