Eight teams, thirty dependencies. Where do you start?
In 200 words, describe how you'd map and reduce inter-team dependencies in a multi-team program. Show the artifact (a dependency matrix or graph) and the architectural moves you'd consider to remove dependencies, not just manage them.
Writing prompt · 200 words · Graded across structure, depth, clarity, judgment
Want the answer graded?
Daily PM gives you one prompt every weekday. Ten focused minutes. A graded answer back. The first three are free.
principle
Inter-team dependencies are the real cost of scaling; map them, then design to reduce them.