More than one Scrum Team is working on a single project or release. How should the Product Backlog be arranged?
More than one Scrum Team is working on a single project or release. How should the Product Backlog be arranged?
When multiple Scrum Teams are working on a single project or release, they should work from a common Product Backlog. This ensures that all the teams are aligned with the same priorities, roadmap, and objectives, and it allows for better synchronization and integration of their work every sprint. Creating separate Product Backlogs would likely lead to misalignment and coordination issues, making it harder to integrate increments effectively.
A is correct
Answer is A
A is correct
Actually I will agree with correct answer B here from a theoretical perspective albeit a developer I know says A is practical
According to the Scrum Guide, Scrum Teams are typically 10 or fewer, with a preference to the smaller size. When Scrum teams become too large, they should consider re-organizing into multiple Scrum Teams supporting a single product. When this happens, the Scrum teams should share a single Product Goal, Product Backlog, Product Owner and a common Definition of Done.