Programme View: Mapping Dependencies Between Projects
Coordinate several related projects.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Map dependencies between projects in a programme. Projects with outputs and needs: [PROJECTS_DEPENDENCIES]. Shared resources: [SHARED_RESOURCES]. Programme goal: [PROGRAMME_GOAL]. Create a dependency matrix with projects on both axes and entries describing what is needed, when, and the risk if late. Identify clusters, circular dependencies, and bottlenecks. Produce an integrated milestone timeline in text and a table of resource conflicts with options. Propose governance: a programme board, cadence, and escalation path. Draft a dependency management routine for the team with a shared register. List the five conversations to hold with project managers this week. Add a method to rank dependencies by risk using the likelihood of delay and the impact on the receiving project, and a one-page dependency report format for the programme board. Include a cadence for dependency review meetings, a list of questions to clarify each dependency with the other project manager, and a rule for recording agreements in writing. Add a worked dependency matrix for four invented projects (identity platform, customer app, data warehouse, reporting) with entries such as the identity platform delivers single sign-on API by week 10 and the customer app needs it by week 12, with two weeks of slack. Mark one circular dependency and show how to break it with an interface agreement. Label it an illustration. Add a dependency register template with fields for ID, providing project, receiving project, deliverable, needed-by date, confidence, owner on each side, status and agreed date, and a weekly 30-minute dependency stand-up agenda. Provide an escalation rule: any dependency with less than one week of slack and a confidence below medium goes to the programme board. Close with a heat map in text that scores each project pair for dependency strength, so the programme board can see where one slipped delivery would hurt most and review that pair first each week.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.