Ownership and dependency mapping
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
produce a map of who owns what and who waits on whom.
Planned topics
- Three lists: capabilities (what the program delivers), owners (one accountable team each), and interfaces (APIs, events, data) with a consumer and a provider.
- Draw dependencies as arrows from consumer to provider; look for chains and for one team with many inbound arrows.
- Serial chains are schedule risk: if three teams wait on one, that team is the critical path.
- Every interface gets an owner and a date before the map is called complete.
Draft outline details
Demonstration
A table: interface | provider | consumers | contract status | date. Example row: stock-changed event | warehouse team | shop orders, search | draft | agree by end of week 2. Plus a sketch of the arrows with the busiest provider circled.
Check your understanding
What does a node with many inbound arrows tell you?
Show answer
It is a bottleneck and a schedule risk to be unblocked early.
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.