Purpose

The framework aims to measure key Product Engineering metrics in order to:

• Enable Squads to monitor their productivity and identify areas for improvement.
• Grant visibility to the organization about the effectiveness and efficiency of the Product Development Flow.

The framework is not meant to measure individual performance.

Glossary

• Story: a task focusing on delivering value to the end user.
• Epic: a large body of work that can be broken down into Stories.
• Bugfix: a task aiming to fix a bug in the Live environment.
• Delivery: a Story or Bugfix released to the end user in the Live environment.
• Deployment: code released in the Stage or Live environment.
• P0 Bug: a critical error, flaw, or unintended behavior that affects one or more critical paths in the Live environment.
• P1 Bug: a non-critical error, flaw, or unintended behavior in the Live environment.
• Incident: a significant disruption in our systems or services, impacting user experience, operations, and reputation.
• Defect: an error, flaw, or unintended behavior that only occurs in the Stage environment.

Metrics

Squads are kindly invited to provide the required data to track the following metrics. Of course, they can track additional metrics if they wish to.

We suggest having an accountable person for each metric tracked in each Squad. Accountability is about implementing the metrics, making sure the tracking works correctly, and monitoring the numbers over time.

Delivery frequency