A.Teach them that it's their responsibility to coordinate with the other teams to integrate and create a shippable product Increment at the end of every Sprint.

B.Identify and manage the dependencies between Scrum Teams.

C.Have the Product Owner work with the tech leads of each team to parse the Product Backlog and minimize overlap in User Stories.

D.Merge the teams and work from a single Sprint Backlog.

A.Extend the Sprint time-box in order to fit the Retrospectives.

B.Suggest reducing the frequency of the Retrospectives.

C.Start facilitating more productive and useful Retrospectives.

D.Comply with the team's decision.

A.The Development Team

B.The Product Owner

C.The Stakeholders

D.The Scrum Master

A.All Sprints must be one month or less and it is optimal to have a consistent Sprint length.

B.The Sprint length is calculated by aggregating the time required to design, code and test.

C.The Sprint length is dependent on the development effort forecasted (amount of items selected) during Sprint Planning.

D.The Sprint Length is defined by the Scrum Master.

A.The level of expertise over the technology to be used, ability to release an Increment to the end users, and the risk of being disconnected from the stakeholders.

B.How often team membership changes and the size of the Development Team.

C.Having consistent Sprint length across all Scrum Teams.