Customer Focus is the lens through which all meaningful delivery is measured. It’s not about opinions. It’s about outcomes. If your product doesn’t change customer behaviour, it doesn’t matter how elegant the code is or how smooth the deployment was.
Customer Focus drives:
- Product strategy grounded in real user need
- Feedback loops that start and end in production
- Backlog prioritisation that reflects outcome over effort
- Decision-making based on evidence, not assumption
If you’re optimising team velocity, delivery cadence, or engineering throughput without validating customer value, you’re reinforcing the wrong system.
Signs of Customer Focus in Practice
- Features are prioritised based on validated user need
- Sprint Goals are framed in terms of impact, not tasks
- Telemetry is used to measure outcomes, not just uptime
- Feedback from production informs backlog decisions
- Stakeholder reviews include customer insights, not just demos
What to Expect
Expect clarity. Expect discipline. Expect work that doesn’t just move fast, but moves in the right direction.
Customer Focus demands that every system of work stays anchored in the only metric that matters: did we deliver something valuable to our customer?
The strongest work on Customer Focus — ranked by substance, not recency. How this is ranked
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 …
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 …
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 …
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, …
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 …
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 …
How Do You Know How Long It Takes to Deliver Value?
Explains how Agile teams can measure and improve Time to Market using key metrics like lead time, cycle time, and time to fix to deliver …
Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics
Explains why story points and velocity can mislead Agile teams, and recommends focusing on throughput, cycle time, and customer value for …
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 …
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 …
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 …
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 …
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, …
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 …
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 …
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, …
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 …
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.
Stop Flying Blind: Why Telemetry Belongs in Your Definition of Done
Stop flying blind after release, learn why telemetry is vital to your Definition of Done and how real feedback drives better software, …
Unlocking Unrealised Value: The Key to Elevating Your Product Development Strategy
Explains how identifying and validating unrealised value, understanding user needs, and rapid feedback loops can enhance product development …
Unlocking Product Value: Why Real User Feedback is Your Best Asset
Real user feedback is essential in product development to validate assumptions, guide improvements, and ensure your product delivers real …
Unlocking Continuous Delivery: How Feature Flags Transform Software Development
Explains how feature flags enable safe, incremental software releases, support continuous delivery, and use user feedback to improve …
Unlocking Code Quality: The Transformative Power of Frequent Deployments
Explores how frequent code deployments improve code quality, reduce technical debt, enable faster feedback, and support iterative, …
Detecting Agile BS
Guidance for identifying genuine agile software development in DoD projects, including key principles, warning signs, essential tools, and …
The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty
Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and …
64 resources, newest first
Mastering Scrum: Effective Planning and Prioritisation for Agile Success
Learn how to plan and prioritise effectively in Scrum by aligning with business goals, assessing value and risk, and keeping a lean, focused …
Why do you think the PSU course has become so popular for product development?
The PSU course bridges the gap in product development by integrating user experience and design into Scrum, enabling teams to deliver more …
How important is DevOps in continuous delivery of value to customers?
Explains how DevOps and Agile work together to enable continuous delivery, rapid feedback, and customer value in software development and …
Why are recessions a great time for organizations to evaluate the opportunity of agile?
Explains why recessions are ideal for organisations to adopt agile, highlighting adaptability, rapid learning, and customer-focused growth …
What is the hardest part of working with a brand-new scrum team?
The biggest challenge with new scrum teams is overcoming misconceptions about scrum and shifting focus from process mechanics to core agile …
Debunking the Scrum Myth: Why "Twice the Work in Half the Time" is a Misleading Promise
Explores why Scrum's "twice the work in half the time" claim is misleading, emphasising value over output and the importance of realistic …
How much of an impact can a strong, skilled product owner have?
A skilled product owner drives teams to build valuable solutions, anticipate customer needs, and deliver features that create real business …
How is agile product development different to waterfall project management?
Compares agile product development and waterfall project management, highlighting differences in decision-making, delivery, customer …
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 …
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, …
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 …
The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty
Evidence-Based Management (EBM) guides organisations to improve value delivery under uncertainty by using empirical goals, measurement, and …