Demo: finding the team that every change waits on
On This Lesson 3 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
locate the main coordination bottleneck with data; prepares SRA-018-LAB1.
Draft outline details
Step by step
- Export a quarter of tickets and pull requests for twelve teams.
- Build the dependency matrix: which team each change needed.
- Compute wait time per team and rank them.
- Planned mistake: conclude "the platform team is slow" from the biggest queue. Fix: check what they own; the queue reflects too many unrelated responsibilities, so the finding is overload and mixed ownership.
- Validate with the team's lead and list the first three changes to test.
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.