We have a separate scrum(front-end) team to handle UI requirements. Sometimes due to urgencies, we end up picking stories in the current sprint which depend on the front-end team.

Whenever dependencies are not resolved timely, our execution gets impacted. What could be the solution in this case?

up vote 6 down vote accepted

In Scrum we look to create product increments each Sprint, not simply to do work. The direct solution to your question from the Scrum Guide is that you should have cross-functional team. That is, all skills needed to deliver a full product increment should be on the team.

There are circumstances where this may not be possible and you are stuck in the constraint. In that situation, you have to coordinate the efforts between the teams to manage the dependencies. However, in every case I've seen with front-end / back-end teams, there are far too many dependencies between them and it is far easier to just reform the teams to be cross-functional.

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.