The vacant-property registry team is composed entirely of GIS analysts and cannot ship a resident-facing slice without waiting on UX, testing, and a separate web group. What should the SM/TC advocate?
Select an answer to reveal the explanation.
Short Explanation
A registry team that is only GIS is a kitchen with only ovens—no one to plate the meal. Residents need a slice they can actually use, not another layer file sitting in a handoff. Mix the skills on one team so a working increment can leave the kitchen.
Full Explanation
High-performing teams are cross-functional enough to deliver a valuable increment. A vacant-property registry staffed only with GIS analysts cannot finish resident-facing work without external UX, test, and web queues, so flow and team performance stall. Adding handoff tickets, requesting a project manager, or demoing GIS layers as if they were resident value all hide the gap. The SM/TC should advocate the missing skills on the team so it can ship end-to-end slices.