You have a Scrum Team that has been working together for over a year. The Development Team consists of eleven members who rarely collaborate and work within their functional boundaries. There are no Sprint Goals and most of the items in the Sprint Backlog are unrelated. The Scrum Team has concluded that it is not possible to create Sprint Goals based on the items in the Product Backlog.
What might explain why the Scrum Team is finding it difficult to craft Sprint Goals? (Choose all that apply.)
The Scrum Team is finding it difficult to craft Sprint Goals due to several reasons. Firstly, if the Product Owner is not empowered to make decisions about items in the Product Backlog nor how they are ordered, the team cannot have a prioritized list of backlog items to create meaningful Sprint Goals. Secondly, if the Product Owner doesn't set objectives that he/she wants to achieve with upcoming Sprints, the team lacks a direction and purpose for their work, which is essential for crafting Sprint Goals. Lastly, the Development Team being too big (eleven members) can lead to communication issues and decreased collaboration, which can hinder the unified effort needed to achieve a Sprint Goal.
11 in a dev team is not recommended
I doubt D should be a correct answer. I don’t think Scrum.org would make up a question asking the candidate to answer “Scrum is not the best framework for the team”… I chose B, C, E.
Indeed, D is counter-intuitive.
On a second thought, D could be correct. Scrum is suitable to solve complex problem. If the work is simple, than Scrum might be overkill.
E could possibly an answer: this large number could be the trigger that they don't collaborate well. This could enforces the team to fill up the Sprint Backlog to meet up the expected velocity. Your starting point will then be 'how to fill up the sprint' rather than 'what should we achieve'. For me: B C E
C and D are OK. But why choose B instead of E?
B: "There are no Sprint Goals and most of the items in the Sprint Backlog are unrelated" This speaks to a product backlog that isn't prioritized D: Self-explanatory E: 11 in a dev team is too large and not recommended
Some of confuse about B But C and D are correct