TL250 – Red Hat Training: Open Practices for your DevOps Journey — Lesson 2: Prioritization, User-Centered Design, Experiments, and Learning Loops

Learning Objectives

• Configure the principal services, objects, workflows, and controls for user perspectives, prioritization, and hypothesis design.
• Apply experiments and learning loops while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• user perspectives: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• prioritization: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• hypothesis design: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• experiments: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• learning loops: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates prioritization, user-centered design, experiments, and learning loops by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for Prioritization, User-Centered Design, Experiments, and Learning Loops 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 user perspectives in the stated scenario.
• Compare two approaches for experiments 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 configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior 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 Prioritization, User-Centered Design, Experiments, and Learning Loops, explain the observed platform behavior, and support the result with a reviewable product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan.