Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 29 of 66
Free Preview · 66 of 218 · questions 1–66 of 218 are free. Sign up free to sync your progress across devices.
Select 3 answers.
This question asks for 3 answers, but our data marks only 1. Compare with the community discussion below for the full answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
A. False — Scrum does not mandate a specific organization into feature teams, even though such teams facilitate its effectiveness. E. False — Measuring productivity by team is not necessarily easier. Scrum prioritizes value delivered over productivity comparisons between teams.
B — Correct: Moving from component teams to feature teams can initially reduce productivity because teams need to learn new skills, responsibilities, and collaboration patterns. C — Correct: Business/stakeholder support is important because feature teams work across multiple technical layers and may require organizational and priority changes. D — Correct: Feature teams reduce dependencies between specialized component teams, which generally reduces handoffs and communication/coordination overhead.
Explanation: A is incorrect → Scrum can still be used with component teams, though feature teams are more effective at delivering end-to-end value. E is incorrect → measuring "productivity per team" is not a Scrum concern, nor is it easier or relevant with feature teams. The key considerations are that moving to feature teams might cause a temporary drop in productivity, requires business support, and ultimately leads to less coordination overhead compared to component teams.