Gathering evidence across 20 teams
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
collect data that shows where the organization really hurts.
Planned topics
- Four evidence streams: delivery metrics, incident history, cost, and engineer experience.
- Mix numbers (lead time, change failure rate) with interviews and survey comments.
- Check data quality; inconsistent definitions across teams are common.
- Share raw findings with teams before conclusions, so they trust the diagnosis.
Draft outline details
Demonstration
a data-source checklist: CI and deploy logs, incident tracker, cloud billing by team, developer survey, onboarding times.
Check your understanding
Why validate data definitions across teams?
Show answer
Teams measure "deploy" or "incident" differently, so naive comparisons mislead.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.