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
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
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 Handoffs Are Killing Your Agility
Excessive handoffs in software development create delays, reduce quality, and harm team morale. Learn how eliminating handoffs boosts …
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 can't stop the signal! But you can ignore it!
Explores why teams ignore clear signals from Agile and Scrum, highlighting how culture and fear hinder continuous improvement and effective …
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 …
Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness
Using Blocked columns on Kanban boards hides workflow issues, causes task stagnation, and reduces transparency. Use tags to indicate …
The Evolution of Agile Learning: Insights from Scrum.org's Webinar
Explores the shift from traditional to immersive Agile learning, highlighting how ongoing, real-world practice and reflection improve …
The 7 Deadly Sins of Agile: A Grecian Odyssey through Modern Software Development
Explores how the seven deadly sins from Greek philosophy mirror common pitfalls in agile software development, offering insights to avoid …
How to Set and Achieve Effective Sprint Goals
Learn how to define, craft, and achieve effective Sprint Goals in Scrum, using frameworks like SMART and OKR to align teams, deliver value, …
The Definition of Done: Ensuring Quality without Compromising Value
Explains how to maintain clear, measurable quality standards with the Definition of Done, while avoiding confusion with acceptance criteria …
Deciphering the Enigma of Story Points Across Teams
Explains why Story Points are subjective and unsuitable for comparing teams, and highlights objective metrics like throughput and value for …
Decoding Scrum Team Work: Balancing Sprint and Refinement Work
Explains how Scrum teams can balance Sprint work and Refinement, with strategies and visual tools to track, manage, and visualise both for …
The Race for Market Responsiveness: A Fresh Perspective on Organisational Agility
Explores why true organisational agility means building custom processes to respond quickly to market changes, not just adopting popular …
Rethinking 'User Stories': A Call for Clarity in Product Backlog Management
Explores why replacing "User Stories" with "Product Backlog Items" improves clarity, flexibility, and transparency in product backlog …
Sculpting the Product Backlog: A Delicate Balance Between Lean Inventory and Future Readiness
Explores how to maintain a lean, transparent product backlog that balances current needs with future readiness, enabling teams to adapt and …
Rethinking Product Backlog: Navigating Through the Weeds of Complexity
Explores how rigid hierarchies in product backlogs can hinder agility, advocating for flatter, value-focused approaches to manage complexity …
Navigating the Future with a Fine-Tuned Product Backlog
Explains how a well-ordered, refined Product Backlog guides Agile teams, supports goal alignment, and ensures value-driven product …
From Unused Gym Memberships to Agile Implementation The Parallels of Misapplied Investments
Explores how superficial adoption of agile in software development mirrors unused gym memberships, highlighting the need for genuine …
Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations
Failing to deliver a usable product each agile iteration leads to lost trust, technical debt, poor adaptability, misaligned expectations, …
How Usable Working Products Are Your Ultimate Weapon Against Risks
Delivering usable, working products frequently is key to reducing risk in Agile. Focus on feedback, automation, and lean practices over …
Risk Mitigation: Agile Usable Products vs Documentation in Traditional Project Management
Compares Agile’s risk mitigation through incremental, usable products with traditional project management’s reliance on documentation, …
A Titanic Misfit: The Alpha Organization's Wasteful Endeavor in Red Markets
Examines how rigid, hierarchical Alpha organisations struggle and waste resources in fast-paced red markets, highlighting the need for …
The Urgent Call for Agile Organisational Transformation
Explores why traditional hierarchical organisations struggle in fast-changing markets and argues for agile, decentralised structures to …
Embrace Uniqueness: Why Creating Your Own Scaling Practices Leads to Business Success
Explores why businesses should develop custom scaling practices tailored to their unique culture and needs, rather than adopting standard …
Announcing Professional Agile Leadership with Evidence-Based Management Training (PAL-EBM) from Scrum.org
Learn about Scrum.org’s new PAL-EBM training, which helps leaders use evidence-based management and custom metrics to align teams with …
Hiring a Professional Product Owner
Explains the key accountabilities, skills, and behaviours required for a Scrum Product Owner, including hiring trends, role requirements, …