From an engineer's perspective, when does Cycle Time begin and end?
Tests if you set Cycle Time boundaries to expose wait states past coding. Strong answer: starts at In Progress, ends at Done or production, includes review/test, excludes backlog queues, and distinguishes from Lead Time. Red flag: starting at ticket creation.
Tests whether you define Cycle Time boundaries that reveal system bottlenecks, not local typing speed. A strong answer starts when work enters In Progress and stops at a verifiable Done such as merged, tested, or in production. It includes review, testing, and deployment because those hide real delays. It excludes backlog queue time, which belongs to Lead Time. The reasoning must connect boundary choice to flow efficiency and exposing wait states. Red flag: conflating Cycle Time with Lead Time or treating it as a personal productivity score.
Read the original → agile-academy.com
- #agile
- #kanban
- #metrics
- #cycle time
- #interview
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.