Search this site
Embedded Files
Delivery Reimagined
  • Product Delivery Playbook
    • Organisational Structure
      • Product Topology Options
      • Squads
    • Experts and Leaders
      • Business Analyst (Software Projects)
      • Quality Chapter Lead
      • Head of Product
      • Project Manager (Software Projects)
      • UX Chapter Lead
      • Engineering Chapter Lead
      • Product Chapter Lead
      • QA Specialist
      • Software Engineer
      • Product Owner
      • UX Design
      • Agile Delivery Manager
      • Portfolio Delivery Lead
      • Head of Delivery (Software)
    • Events
      • Product Performance
      • Product Release Planning
      • Product Risks, Issues, and Dependencies (RID)
      • Leaders Sync
      • Retrospectives
      • Product Review
      • Daily Sync
      • Product Planning
      • Backlog Refinement Session
    • Planning and Tracking
      • Backlogs
      • Cadence
      • Product Benefits
      • User Stories
      • Estimation
      • Risks, Issues, and Dependencies
    • Tools
      • 3 Steps to Standardising work management
    • Insights
      • Manage variables
      • Burndown charts
      • DORA Metrics
      • Cycle time
      • FACT
  • Executive Zone
    • Project to Product
      • CAPEX to OPEX
        • Sustainable and Continuous Delivery with OPEX
        • Hybrid of OPEX and CAPEX
        • Product Delivery with CAPEX
      • Tasks to Outcomes
        • Prioritize outcomes
        • OKR Towards Outcomes
        • Break down work
      • Teams as Assets
        • Roles in Software
        • Cross Functional
        • High performing teams
      • Managers to Owners
        • Intent led
        • Customer Centric
        • Two in a box leadership
    • Measure what Matters
      • Verticle and Horizontal Alignment
        • Managing Up
        • Dependencies
        • Epics and OKRs
      • Start Finishing
        • Utilization Limits
        • Flow
        • Shared Heroes
      • Accountability and Collaboration
        • Psychological Safety
        • Building Clarity
        • Meetings
      • Measurable Progress
        • Team Performance
        • Burndown
        • Project Manager Bias
    • Team Topology
      • Collaboration and Communication
        • Stop separating people
        • Thrive together
        • Software is capital
      • Automate what is repeatable
        • Maintain
        • Releases
        • Sustainable Quality
      • Continuous Monitoring and Feedback
        • Beyond Launch
        • Listening to Your Customers
        • Root Cause Analysis
    • Books
      • Team Topologies by Matthew Skelton
      • Project to Product by Mik Kersten
      • Measure what matters by John Doerr
      • The Phoenix Project by Gene Kim et al
      • Atomic Habits by James Clear
      • User Stories by Mike Cohn
      • The DevOps Handbook by Gene Kim
      • Software Development by Mike Cohn
      • Scrum by Jeff Sutherland
      • The Cooperative Game by Alistair Cockburn
      • Black Box Thinking by Matthew Syed
      • Dare to Lead by Brene Brown
      • Leading Beyond Change by Michael Sahota
    • Videos
Delivery Reimagined
  • Product Delivery Playbook
    • Organisational Structure
      • Product Topology Options
      • Squads
    • Experts and Leaders
      • Business Analyst (Software Projects)
      • Quality Chapter Lead
      • Head of Product
      • Project Manager (Software Projects)
      • UX Chapter Lead
      • Engineering Chapter Lead
      • Product Chapter Lead
      • QA Specialist
      • Software Engineer
      • Product Owner
      • UX Design
      • Agile Delivery Manager
      • Portfolio Delivery Lead
      • Head of Delivery (Software)
    • Events
      • Product Performance
      • Product Release Planning
      • Product Risks, Issues, and Dependencies (RID)
      • Leaders Sync
      • Retrospectives
      • Product Review
      • Daily Sync
      • Product Planning
      • Backlog Refinement Session
    • Planning and Tracking
      • Backlogs
      • Cadence
      • Product Benefits
      • User Stories
      • Estimation
      • Risks, Issues, and Dependencies
    • Tools
      • 3 Steps to Standardising work management
    • Insights
      • Manage variables
      • Burndown charts
      • DORA Metrics
      • Cycle time
      • FACT
  • Executive Zone
    • Project to Product
      • CAPEX to OPEX
        • Sustainable and Continuous Delivery with OPEX
        • Hybrid of OPEX and CAPEX
        • Product Delivery with CAPEX
      • Tasks to Outcomes
        • Prioritize outcomes
        • OKR Towards Outcomes
        • Break down work
      • Teams as Assets
        • Roles in Software
        • Cross Functional
        • High performing teams
      • Managers to Owners
        • Intent led
        • Customer Centric
        • Two in a box leadership
    • Measure what Matters
      • Verticle and Horizontal Alignment
        • Managing Up
        • Dependencies
        • Epics and OKRs
      • Start Finishing
        • Utilization Limits
        • Flow
        • Shared Heroes
      • Accountability and Collaboration
        • Psychological Safety
        • Building Clarity
        • Meetings
      • Measurable Progress
        • Team Performance
        • Burndown
        • Project Manager Bias
    • Team Topology
      • Collaboration and Communication
        • Stop separating people
        • Thrive together
        • Software is capital
      • Automate what is repeatable
        • Maintain
        • Releases
        • Sustainable Quality
      • Continuous Monitoring and Feedback
        • Beyond Launch
        • Listening to Your Customers
        • Root Cause Analysis
    • Books
      • Team Topologies by Matthew Skelton
      • Project to Product by Mik Kersten
      • Measure what matters by John Doerr
      • The Phoenix Project by Gene Kim et al
      • Atomic Habits by James Clear
      • User Stories by Mike Cohn
      • The DevOps Handbook by Gene Kim
      • Software Development by Mike Cohn
      • Scrum by Jeff Sutherland
      • The Cooperative Game by Alistair Cockburn
      • Black Box Thinking by Matthew Syed
      • Dare to Lead by Brene Brown
      • Leading Beyond Change by Michael Sahota
    • Videos
  • More
    • Product Delivery Playbook
      • Organisational Structure
        • Product Topology Options
        • Squads
      • Experts and Leaders
        • Business Analyst (Software Projects)
        • Quality Chapter Lead
        • Head of Product
        • Project Manager (Software Projects)
        • UX Chapter Lead
        • Engineering Chapter Lead
        • Product Chapter Lead
        • QA Specialist
        • Software Engineer
        • Product Owner
        • UX Design
        • Agile Delivery Manager
        • Portfolio Delivery Lead
        • Head of Delivery (Software)
      • Events
        • Product Performance
        • Product Release Planning
        • Product Risks, Issues, and Dependencies (RID)
        • Leaders Sync
        • Retrospectives
        • Product Review
        • Daily Sync
        • Product Planning
        • Backlog Refinement Session
      • Planning and Tracking
        • Backlogs
        • Cadence
        • Product Benefits
        • User Stories
        • Estimation
        • Risks, Issues, and Dependencies
      • Tools
        • 3 Steps to Standardising work management
      • Insights
        • Manage variables
        • Burndown charts
        • DORA Metrics
        • Cycle time
        • FACT
    • Executive Zone
      • Project to Product
        • CAPEX to OPEX
          • Sustainable and Continuous Delivery with OPEX
          • Hybrid of OPEX and CAPEX
          • Product Delivery with CAPEX
        • Tasks to Outcomes
          • Prioritize outcomes
          • OKR Towards Outcomes
          • Break down work
        • Teams as Assets
          • Roles in Software
          • Cross Functional
          • High performing teams
        • Managers to Owners
          • Intent led
          • Customer Centric
          • Two in a box leadership
      • Measure what Matters
        • Verticle and Horizontal Alignment
          • Managing Up
          • Dependencies
          • Epics and OKRs
        • Start Finishing
          • Utilization Limits
          • Flow
          • Shared Heroes
        • Accountability and Collaboration
          • Psychological Safety
          • Building Clarity
          • Meetings
        • Measurable Progress
          • Team Performance
          • Burndown
          • Project Manager Bias
      • Team Topology
        • Collaboration and Communication
          • Stop separating people
          • Thrive together
          • Software is capital
        • Automate what is repeatable
          • Maintain
          • Releases
          • Sustainable Quality
        • Continuous Monitoring and Feedback
          • Beyond Launch
          • Listening to Your Customers
          • Root Cause Analysis
      • Books
        • Team Topologies by Matthew Skelton
        • Project to Product by Mik Kersten
        • Measure what matters by John Doerr
        • The Phoenix Project by Gene Kim et al
        • Atomic Habits by James Clear
        • User Stories by Mike Cohn
        • The DevOps Handbook by Gene Kim
        • Software Development by Mike Cohn
        • Scrum by Jeff Sutherland
        • The Cooperative Game by Alistair Cockburn
        • Black Box Thinking by Matthew Syed
        • Dare to Lead by Brene Brown
        • Leading Beyond Change by Michael Sahota
      • Videos

Product Delivery Playbook >> Insights >> FACT

In the world of software development, cycle time is a crucial metric that measures the total time it takes for a team to deliver a change to customers. It’s the period from the moment work begins on a feature to the instant it’s successfully released. This metric provides a clear, objective measure of a team's efficiency and responsiveness. A short cycle time indicates that a team is highly agile, able to quickly respond to market demands and customer feedback. Conversely, a long cycle time can signal bottlenecks, inefficient processes, or technical debt that slow down development.

Understanding Feature Average Cycle Time (FACT)

While cycle time can be measured for any single task, a more powerful and practical metric is the Feature Average Cycle Time (FACT).

As the name suggests, FACT is the average cycle time for all features delivered over a fixed cadence. This cadence is usually a planning increment (PI), which typically spans a quarter, or another predefined period.

The formula for FACT is:

FACT = ( Σ Cycle Time of all Features ) / ( Total Number of Features )

Where:

  • Σ Cycle Time of all Features is the sum of the cycle times for every feature completed within the defined cadence.

  • Total Number of Features is the total count of features completed within that same cadence.

By averaging the cycle time over a quarter, FACT smooths out the noise from individual features and provides a reliable, high-level view of a team's performance. It helps answer critical questions like:

  • How long does it typically take our team to deliver a feature to customers?

  • Are we getting faster or slower over time?

  • What is our delivery rhythm?

FACT is an excellent tool for strategic planning. It helps product managers and stakeholders forecast when features might be ready and provides a data-driven basis for setting realistic expectations. When used with other DORA metrics,FACT helps organizations create a comprehensive picture of their delivery performance, identifying areas for improvement and celebrating successes.

Further reading;

  • Manage variables

  • Burndown Charts

  • A Guide to DORA Metrics and Their Role in End-to-End Delivery

  • Cycle time

  • FACT

Report abuse
Page details
Page updated
Report abuse