Unverified

This hasn’t been verified by an expert from worklab.dev since Mar 29, 2023.

Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

Agility: Cycle time

image.png

Purpose

Velocity: resolve the issues as fast as possible, while being aligned with quality standards.

Expectation

Cycle time should be around 5-6 days.

How an indicator is measured

Cycle time = average duration of issues in following states: in progress, code review, testing, acceptance, deployed.

Action

If Cycle time is high, the cost of issues implementation is high. It usually signals a mediocre preparation of the sprint.

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.