Product Development is the systematic process of delivering valuable and usable products through iterative learning, customer feedback, and continuous improvement. It encompasses the alignment of strategy, discovery, and delivery to maximise outcomes while minimising risk. This concept is crucial as it enables teams to respond effectively to changing market demands and customer needs, fostering an environment where innovation can thrive.
By integrating practices from Agile, Lean, and DevOps, Product Development promotes a culture of collaboration and transparency, allowing cross-functional teams to work cohesively towards shared goals. It emphasises the importance of understanding customer feedback loops, which inform product iterations and enhancements, ensuring that the end product not only meets but exceeds user expectations.
The long-term, systemic nature of Product Development means that it is not merely about delivering a product but about creating a sustainable framework for ongoing value delivery. This approach encourages teams to embrace experimentation and learning, leading to improved efficiency and effectiveness in product delivery. By focusing on continuous improvement and adaptability, organisations can cultivate resilience and maintain a competitive edge in an ever-evolving landscape. The emphasis on value delivery ensures that every effort contributes meaningfully to the organisation’s strategic objectives, reinforcing the importance of a well-defined Product Development process in achieving long-term success.
The strongest work on Product Development — 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 …
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 …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
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 …
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 …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward
Struggling with technical debt? Discover practical ways to tackle legacy systems, boost team morale, and deliver value, without grinding to …
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 …
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 Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
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 …
Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win
Unlock your team's true potential, discover why a powerful definition of done drives real business impact, customer value, and lasting …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Detecting Agile BS
The Scrum Guide (February 2010)
The Evidence-Based Management Guide 2020: Improving Value Delivery under Conditions of Uncertainty
Kendall Guide - A System of Work for AI Adoption
OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning
Evidence-Based Portfolio Management
605 resources, newest first
Agile and Scrum are often misunderstood
Agile and Scrum expose underlying team and workflow issues, helping organisations address real problems rather than masking dysfunction with …
The Role of Agency in Scrum: Why Self-Management Without Agency is a Lie
Explains why true Scrum requires real team agency, not just self-management in name, and how lacking agency leads to ineffective, …
let-us do the maths
Explains how slow product release cycles delay feature delivery, risk losing relevance, and create competitive disadvantages, highlighting …
Too much refinement wastes time
Balancing backlog refinement prevents wasted effort and chaos. Aim for just enough detail so developers can plan sprints confidently without …
Not all surprises in product development are true unknowns
Many product development surprises stem from poor backlog management, not true unknowns. Regular refinement and reflection help teams …
Unlocking Legacy Systems: How to Embrace Automation and Drive Innovation
Learn how to automate legacy systems by shifting organisational mindset, adopting DevOps practices, and making incremental improvements to …
No successful company thrives by copying others’ ways of working
Successful companies thrive by creating unique ways of working, not by copying frameworks. Tailor your approach to fit your organisation’s …
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 …
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 …
Agile without a usable working product is just expensive theatre
Highlights the importance of delivering a usable product each sprint in Agile, warning against focusing on process over outcomes and …
You don’t own your market
Explains why businesses must prioritise customer needs and agility to stay relevant, avoid missed opportunities, and remain competitive in a …
Most companies still get Product Ownership wrong
Many organisations misunderstand Product Ownership, treating it as simple backlog management instead of a strategic, accountable role …
The market isn’t slowing down for anyone
Explores why organisational responsiveness and real-time decision-making are crucial for staying competitive, highlighting the risks of …
Hiring a Product Owner? Avoid copying job specs from the internet
Learn what makes an effective Product Owner, why generic job specs fall short, and which key responsibilities and skills are essential for …
Building the wrong thing is worse than fixing a bug
Most features don’t deliver value. Short feedback loops and real user input help teams avoid wasted effort by ensuring they build what users …
Navigating the Legacy System Dilemma: Balancing Stability and Innovation for Modernisation Success
Learn how to modernise legacy systems by balancing stability and innovation, managing technical debt, and adopting gradual, sustainable …
A great backlog isn’t just a list of tasks
Learn how an effective backlog guides product strategy, prioritises value, and supports decision-making, rather than serving as a simple …
A great Product Owner drives product strategy, not just manages the backlog
Explains how effective Product Owners shape product strategy using accountability, awareness, acceptance, access, and adaptability, not just …
Navigating the Legacy System Labyrinth: Strategies for Modernisation Success
Explore practical strategies for overcoming legacy system challenges, addressing technical debt, compliance, integration, and guiding …
If every release feels high-risk, you lack a true Definition of Done
Releases feel risky when teams lack a clear Definition of Done. Learn how a strong DoD ensures stress-free, reliable software delivery with …
Executives want predictability
Lack of a clear, enforced Definition of Done leads to hidden risks, unreliable forecasts, and eroded trust in delivery, undermining …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
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 …
The True Role of a Scrum Master Beyond Facilitation
Explains how a Scrum Master drives team improvement, removes obstacles, and leads organisational change, going far beyond basic facilitation …
Why Teams Claim Self-Management to Avoid Alignment Discussions
Explores how teams misuse self-management to dodge alignment, clarifying that true autonomy requires accountability, shared goals, and …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Technical debt isn’t just messy code
Technical debt includes slow feedback, fragile systems, and manual processes that hinder progress. Addressing it early with automation and …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Agile Is Not Easier Than Traditional Methods: Common Misconceptions
Explains why Agile methods are often more challenging than traditional ones, highlighting common misconceptions, required discipline, and …