PSM-II · Question #1
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…
The correct answer is B. The Product Owner is not empowered to make decisions about items in the Product Backlog nor C. The Product Owner doesn't set objectives that he/she wants to achieve with upcoming Sprints. D. Scrum might not be the best framework for this team. Many people misinterpret the Scrum Guide as stating the Development Team size is limited to 3- 9 members. In reality, it only states that there is inherent risk attached to having less than 3 members and more than 9 members. As the number of members increases, the lines of…
Question
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.)
Options
- AThe Sprints are too long.
- BThe Product Owner is not empowered to make decisions about items in the Product Backlog nor
- CThe Product Owner doesn't set objectives that he/she wants to achieve with upcoming Sprints.
- DScrum might not be the best framework for this team.
- EThe Development Team is too big.
How the community answered
(60 responses)- A28% (17)
- B58% (35)
- E13% (8)
Explanation
Many people misinterpret the Scrum Guide as stating the Development Team size is limited to 3- 9 members. In reality, it only states that there is inherent risk attached to having less than 3 members and more than 9 members. As the number of members increases, the lines of communication also increase. This can be calculated using the Group intercommunication formula: n(n - 1) / 2 where n is the number of members. Some teams are able to handle the risk and "synergize" whereas others Saying that, the relationship between defining a Sprint Goal and Development Team size is But the relationship between the ordering of the Product Backlog, the PO having clear objectives, and the Sprint Goal are direct. The Product Owner typically comes to the Sprint Planning with a business objective in mind and Product Backlog items related to the business objective. After deciding what can be done for the upcoming Sprint, the Scrum Team will craft a Sprint Goal that would be met through the implementation of the items. This is not dependent on the size of the team nor length of the Sprint. Scrum is also a framework that's fit for purpose. Some projects/products are not fit for Scrum... or, better stated, Scrum is not suitable for all projects/products.
Topics
Community Discussion
No community discussion yet for this question.