TL250 – Red Hat Training: Open Practices for your DevOps Journey — Lesson 1: Discovery, Stakeholder Alignment, Outcomes, Value, and Problem Framing

Learning Objectives

• Explain the architecture, purpose, dependencies, and expected behavior of stakeholder alignment, outcome definition, and value mapping.
• Apply problem framing and assumption discovery while preserving reviewable technical evidence.
• Recognize and correct the condition where an unstated prerequisite or ownership gap causes the initial design to be incomplete.

Detailed Topics

• stakeholder alignment: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• outcome definition: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• value mapping: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• problem framing: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• assumption discovery: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates discovery, stakeholder alignment, outcomes, value, and problem framing by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how an unstated prerequisite or ownership gap causes the initial design to be incomplete and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Establish a controlled baseline for Discovery, Stakeholder Alignment, Outcomes, Value, and Problem Framing 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 stakeholder alignment in the stated scenario.
• Compare two approaches for problem framing 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 architecture, scope, identities, prerequisites, and starting conditions separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that an unstated prerequisite or ownership gap causes the initial design to be incomplete as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required architecture, scope, identities, prerequisites, and starting conditions 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 Discovery, Stakeholder Alignment, Outcomes, Value, and Problem Framing, explain the observed platform behavior, and support the result with a reviewable product discovery canvas, prioritized experiment backlog, delivery metrics, and team improvement plan.