You can resolve this via below steps:
1. You can add an issue type "dependency" on all projects.
2. Use this issue type to document the project-level dependency.
3. The dependency issue description should state what is the dependency of your project on the other project.
4. Provide a due date by when you expect this dependency to be available for your project.
5. Create such issues on all projects to document the dependency.
6. Now create a dashboard where you can view dependency issue type across all projects.
7. Use this board in the SOS calls where SMs and POs can provide more information and discuss the dependency resolution steps. (keep periodic SOS call to review this board)
8. Post sprint planning each SM can give the dependency resolution due date on the dependency (Add custom due date field for the same)
Note: Link the working issues(Story) on this dependency so that in the SOS call you can review the progress of each projects on where they are in resolving the dependencies.
Linking issues will let you know the dependency is at what state - developement or testing or ready for UAT or Prod or released/completed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.