Running a scrum of scrums is a way of doing this, but there are plenty. Once the task is completed, ensure the other teams are aware of it.Once a task that will impact more than one story becomes priority on the backlog, ensure the broader aspect of solution proposed is considered, to avoid situations where the task delivered only fits one story but not all of them.During sprint plan, assess which tasks are dependent by more than one user story one one story that depends on this task is prioritize, make sure the other stories are aware of it (if you use a software to track stories and tasks, a simple way is using links between them).when decoupling is not possible, try to have clear interfaces between applications (technologies, as it seems in your cases) This way, one implementation will be valid for all applications so long they adhere to this common interface.Avoid cross-dependency as much as possible it's a no brainer, but sometimes you need someone with a pair of fresh eyes to review the way the platform is built to propose some decoupling.Specific actions to take into account on how to manage these dependencies: We're running a project with four teams sharing the same platform, and the solution boils down to communicate.
The cross-team dependency is a known problem on large scale projects.
0 kommentar(er)
