MENU
Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)
Suggested Answer: C
Get Premium PSM-I Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
A, B and D are not good answers because they imply a command-and-control approach that contradicts Scrum's values of respect, openness, and self-organization. Management in Scrum is not supposed to micromanage, judge, or interfere with the work of the Developers, but rather support them and enable them to deliver value.
33 comments · newest first
RY
Ryann
11 months ago
Productivity per team is easier to measure with feature teams, for sure!
JO
Josphine
11 months ago
Getting support from the business side is crucial, no doubt about it.
DA
Daniela
11 months ago
Wait, you can't do Scrum without feature teams? That sounds extreme!
TA
Tammara
11 months ago
I disagree, I think productivity might actually drop at first.
MA
Mari
11 months ago
Feature teams definitely reduce communication overhead!
AN
Anjelica
12 months ago
I’m a bit confused about the productivity calculations with feature teams. I thought it was more complex, but maybe option E is right?
SA
Sang
12 months ago
I feel like we practiced a question about communication overhead before, and I think feature teams help reduce that. So maybe option D is a good choice.
ME
Merissa
12 months ago
I’m not entirely sure, but I think getting support from the business side is crucial when making such changes. That sounds like option C.
KA
Kati
1 year ago
I remember discussing how moving to feature teams can actually lead to some initial productivity dips, so I think option B might be relevant here.
KR
Kristal
1 year ago
I feel pretty confident about this one. The main things to think about are the potential productivity impact, the communication overhead, and getting buy-in from the business. As long as we address those, moving to feature teams should be a good call.
AN
Anglea
1 year ago
Okay, let's see. The key things I'd focus on are how this change might impact productivity, whether it will reduce communication overhead, and making sure we get the business on board. Those seem like the most important factors to weigh.
WH
Whitley
1 year ago
Hmm, I'm a little unsure about this one. I know feature teams are important for Agile, but I'm not sure if that's the only factor to consider here. I'll need to think through the pros and cons more carefully.
QU
Quentin
1 year ago
This seems like a pretty straightforward question. I'd focus on the key considerations like productivity, communication overhead, and getting buy-in from the business.
MA
Ma
1 year ago
Hmm, this looks like a tricky one. I'll need to carefully work through the calculations to determine the adjusted present value of the expansion.
PE
Penney
1 year ago
Ah, I remember learning about this in class. The extended refund window with a pro-rated restocking fee is a common Cisco Meraki licensing benefit. I'll select option A.
LO
Loren
1 year ago
I remember that for finance leases, we definitely have to consider the finance cost and depreciation in the P&L, but I'm not completely sure about the exact wording.
DA
Dalene
1 year ago
E) With feature teams, it is easier to calculate the productivity per team? Oh, the joys of metrics! I can already see the spreadsheets and graphs being whipped out. Just don't forget to factor in the occasional coffee break for sanity's sake.
DA
Dalene
1 year ago
E) With feature teams, it is easier to calculate the productivity per team.
CE
Celestine
1 year ago
C) Getting support from the business side first helps.
RI
Rickie
1 year ago
A) You cannot do Scrum without feature teams.
WI
Wilda
1 year ago
D) Feature teams have less communication overhead? That's the dream, right? I'm picturing a world where developers actually talk to each other instead of playing email tag all day.
BR
Bronwyn
1 year ago
C) Getting support from the business side first helps? Absolutely! Having the business on board is key when making such an organizational change. Otherwise, you're just setting yourself up for a headache.
LA
Lamar
1 year ago
D) Feature teams have less communication overhead.
KA
Karrie
1 year ago
C) Getting support from the business side first helps.
CA
Cassie
1 year ago
A) You cannot do Scrum without feature teams.
NO
Novella
1 year ago
B) Productivity may suffer when making this kind of move? That's a valid concern, but I've also seen feature teams improve productivity by reducing communication overhead and increasing cross-functional collaboration.
PO
Pok
1 year ago
D) Feature teams have less communication overhead.
KI
Kindra
1 year ago
C) Getting support from the business side first helps.
ST
Stefany
1 year ago
A) You cannot do Scrum without feature teams.
RE
Rex
1 year ago
A) You cannot do Scrum without feature teams? That's a bit of a stretch. Sure, feature teams can help with Scrum, but there are plenty of successful Scrum teams that aren't organized that way.
OZ
Ozell
2 years ago
But won't productivity suffer if we move away from component teams?
TA
Tabetha
2 years ago
I agree, that would definitely help in the transition.
BR
Brande
2 years ago
I think we should consider getting support from the business side first.