Empirical Process Control is a foundational concept that emphasises decision-making based on observation and experimentation rather than assumptions. It is integral to Agile, Lean, and DevOps methodologies, enabling teams to adapt their processes and outputs through continuous inspection and transparency. By relying on real data and feedback, organisations can identify what works and what doesn’t, fostering a culture of learning and improvement.
This approach allows teams to deliver value predictably and sustainably, as they can adjust their strategies based on actual performance rather than theoretical models. It encourages a mindset of experimentation, where hypotheses are tested in practice, leading to informed decisions that enhance product quality and customer satisfaction.
Empirical Process Control is not merely a tactical tool; it is a long-term, systemic enabler of organisational agility. It cultivates an environment where teams can respond swiftly to changing conditions, ensuring that they remain aligned with customer needs and market dynamics. This adaptability is crucial in today’s fast-paced development landscape, where the ability to pivot based on evidence can significantly impact success. By embedding empirical practices into their workflows, organisations can achieve a more resilient and responsive operational model that prioritises value delivery and continuous improvement.
The strongest work on Empirical Process Control — 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 …
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 …
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 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 …
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 …
Release planning and predictable delivery
Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Every delay increases the risk of failure
Delaying software releases increases failure risk. Frequent, small releases improve success rates, adaptability, and recovery, as shown 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 …
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 …
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 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 …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, 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 …
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
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 …
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 …
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 …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics
Stop guessing, start making data-driven decisions in Azure DevOps. Discover tools, tips, and insights to make your work visible and your …
Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership
Stop chasing tech trends. Learn how evidence, visibility, and clarity empower tech leaders to make confident, strategic decisions, beyond …
Maximising Product Value: The Power of Hypothesis-Driven Engineering
Explores how hypothesis-driven engineering helps teams maximise product value by testing ideas, measuring outcomes, and learning from …
Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development
Explores how breaking features into small experiments boosts software delivery, enabling teams to deliver more features, reduce risk, and …
Unlocking Continuous Improvement: How Metrics and Visualisation Drive Workflow Success
Explores how using metrics and visual tools enhances workflow transparency, helps identify improvement areas, and supports a culture of …
Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile
Empowering teams to adapt requirements based on user feedback is key to true agility. Learn why backlog updates and team engagement drive …
The Fallacy of Equating Agility with Speed: What Agile Really Means
Explains why Agile is not about speed but about prioritising valuable work, adapting to feedback, and avoiding wasted effort to deliver …
The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty
Kendall Guide - A System of Work for AI Adoption
88 resources, newest first
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 …
Kendall Guide - A System of Work for AI Adoption
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 Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics
Stop guessing, start making data-driven decisions in Azure DevOps. Discover tools, tips, and insights to make your work visible and your …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, 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 …
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 …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership
Stop chasing tech trends. Learn how evidence, visibility, and clarity empower tech leaders to make confident, strategic decisions, beyond …
The Myth of Knowing Everything Upfront in Software Development
Software development thrives on continuous discovery and adaptation; upfront planning can’t predict everything. Embrace uncertainty, deliver …
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 …
Stop treating the end of the Sprint like a finish line
The end of a Sprint is a checkpoint for review and adaptation, not a deadline. Focus on flow, learning, and continuous improvement over …
Scrum isn’t limited to building features
Scrum can drive organisational change, not just product features, by using backlogs, teams, and feedback to enable real, evidence-based …
David thought he already knew Scrum
Discover why experienced Scrum practitioners often misunderstand core principles, and how revisiting Scrum fundamentals restores clarity, …
Scrum doesn’t stop you from optimising flow
Explains how Scrum supports continuous flow and agility by prioritising Sprint Goals, Done increments, CI/CD practices, and outcomes over …
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 …
Microsoft shift from 2-year cycles to 3-week Sprints caused team anxiety
Microsoft’s switch to 3-week Sprints increased team anxiety due to greater transparency, exposing inefficiencies but enabling faster, more …
Scrum is not a process it is a social technology designed to expose dysfunction
Explains how Scrum reveals team dysfunctions by clarifying roles and accountability, highlighting its purpose to expose issues that hinder …
Every delay increases the risk of failure
Delaying software releases increases failure risk. Frequent, small releases improve success rates, adaptability, and recovery, as shown by …
Without Delivery, There Is No Value
Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …
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 …
Maximising Product Value: The Power of Hypothesis-Driven Engineering
Explores how hypothesis-driven engineering helps teams maximise product value by testing ideas, measuring outcomes, and learning from …
Unlocking Success: How Small Experiments Transformed Feature Delivery from 25 to 150 in Software Development
Explores how breaking features into small experiments boosts software delivery, enabling teams to deliver more features, reduce risk, and …
Unlocking Continuous Improvement: How Metrics and Visualisation Drive Workflow Success
Explores how using metrics and visual tools enhances workflow transparency, helps identify improvement areas, and supports a culture of …
Are Your Teams Empowered to Change Requirements Based on User Feedback? If Not, You’re Probably Not Very Agile
Empowering teams to adapt requirements based on user feedback is key to true agility. Learn why backlog updates and team engagement drive …