TL250 – Red Hat Training: Open Practices for your DevOps Journey — Lesson 4: Metrics, Retrospectives, Continuous Improvement, Facilitation, and Roadmap

Learning Objectives

• Operate, diagnose, document, recover, and improve delivery metrics, retrospectives, and facilitation.
• Apply continuous improvement and roadmap while preserving reviewable technical evidence.
• Recognize and correct the condition where the technical result is restored but monitoring, rollback, evidence, ownership, or handover remains incomplete.

Detailed Topics

• delivery metrics: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• retrospectives: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• facilitation: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• continuous improvement: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• roadmap: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates metrics, retrospectives, continuous improvement, facilitation, and roadmap by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how the technical result is restored but monitoring, rollback, evidence, ownership, or handover remains incomplete and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Conduct an operational acceptance review for Metrics, Retrospectives, Continuous Improvement, Facilitation, and Roadmap and add the verified result to the product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences delivery metrics in the stated scenario.
• Compare two approaches for continuous improvement and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check monitoring, troubleshooting, rollback, ownership, evidence, and handover separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that the technical result is restored but monitoring, rollback, evidence, ownership, or handover remains incomplete as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required monitoring, troubleshooting, rollback, ownership, evidence, and handover were checked and recorded.
• The normal path and a course-specific exception were tested.
• The product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Metrics, Retrospectives, Continuous Improvement, Facilitation, and Roadmap, explain the observed platform behavior, and support the result with a reviewable product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan.