产品交付周期计算公式_使用周期时间指标优化工程团队的交付

产品交付周期计算公式

Delivery health is a key element of a healthy engineering team. At SafetyCulture we are not simply looking for delivery health. We aspire for world-class level excellence in how we deliver value to customers.

交付健康是健康的工程团队的关键要素。 在SafetyCulture，我们不仅仅是在寻找分娩的健康状况。 我们渴望在为客户提供价值方面达到世界一流水平。

This is particularly important to me as an engineering manager accountable for product delivery. I need methods and tooling that make it easy to support multiple cross-functional teams building some of the most critical components of our flagship iAuditor product. I recently had the opportunity to experiment with exactly that. The experiment was successful and I hope my learnings are useful to you.

作为负责产品交付的工程经理，这对我尤为重要。 我需要能够轻松支持多个跨职能团队构建我们旗舰iAuditor产品的一些最关键组件的方法和工具。 最近，我有机会对此进行了实验。 实验是成功的，希望我的学习对您有所帮助。

In a fast paced agile environment such as SafetyCulture the flow of a team’s work was identified as a key productivity indicator reflecting delivery health. In simple terms, you can think about flow as the average rate of getting things done as a team. Flow is the rhythm or pulse of the team’s delivery engine. For example, at SafetyCulture our product teams aim to deliver customer value every 3–5 days on average.

在诸如SafetyCulture之类的快速敏捷环境中，团队的工作流程被确定为反映交付健康状况的关键生产力指标。 简单来说，您可以将流程视为团队完成工作的平均速度。 流程是团队交付引擎的节奏或脉动。 例如，在SafetyCulture，我们的产品团队旨在平均每3-5天为客户提供价值。

Flow is the rhythm or pulse of the team’s delivery engine

流程是团队交付引擎的节奏或脉搏

Optimising for flow is better than other agile measurements such as velocity based on story points as it works in the language of the customer (wall clock time). Other benefits include improved predictability, streamlined team operations, boosted team morale and the ability to be truly agile when process or behavioural change is needed. For a detailed analysis of the benefits of flow versus other delivery health metrics I highly recommend Daniel Vacanti’s book “Actionable Agile Metrics for Predictability: An Introduction”.

针对流量进行优化比其他敏捷测量(例如基于故事点的速度