LEARN. PRACTICE. GROW.Concept and mechanism
DevOps requires making the work path visible from request to production outcome. In the Azure Boards widget, lead time starts at item creation and ends at completion; cycle time starts when work enters progress. These definitions should not be confused with other lead-time metrics using commit and deployment as endpoints. A reopened item retains measurement from first start to final closure, including intervening time. If the team only updates states at the end, the metric can improve without actual improvement. Maintain state criteria and observe distribution, delays, and rework rather than rewarding one average alone.
Guided application
For a fictional funds release, link work item, review, pipeline run, artifact, and deployment. Support needs to identify actually delivered contents rather than just the person on duty. Include limitations, validation, recovery, and contacts in release notes. A notification in three channels does not guarantee response if none has an owner. Define action and escalation for relevant signals. In international handover, use clear English and distinguish observed facts, hypotheses, and next actions. Completing implementation does not prove RUN autonomy; rehearse access, diagnosis, and recovery with the receiving team. Retain temporary support and exit criteria if transfer is phased.
Created on day 2, started on day 5, completed on day 11: nine-day lead time and six-day cycle time for equal times.
Common pitfalls
Undefined metrics; late state updates; more deployments as quality; handover as sending files.
Related topics: Git, review, and recovery · Artifacts, dependencies, and agents
Measure flow and retain a verifiable chain through operations.
Reference: AZ-400 July 2026 study guide · AZ-400 objectives 2026-07-27