Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum PSM-I Exam - Topic 4 Question 64 Discussion

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.)
C) Getting support from the business side first helps.
A) You cannot do Scrum without feature teams.
B) Productivity may suffer when making this kind of move.
D) Feature teams have less communication overhead.
E) With feature teams, it is easier to calculate the productivity per team.

Scrum PSM-I Exam - Topic 4 Question 64 Discussion

Actual exam question for Scrum's PSM-I exam
Question #: 64
Topic #: 4
[All PSM-I Questions]

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.)

Show Suggested Answer Hide Answer
Suggested Answer: C

The best answer is C. The function or purpose of management in Scrum is to present the Scrum Teams with insights and resources that help them improve. According to the article What is the Function or Purpose of Management in Scrum?, management is still critical to providing vision, securing resources, hiring talent, training teams, removing roadblocks, and continuously improving. Management also encourages collaboration and establishes Scrum Team autonomy, which are essential for Scrum's values and principles.

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.


by Jerry at Jan 25, 2024, 04:31 AM

Limited Time Offer

25%

Off

Get Premium PSM-I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ryann
8 months ago
Productivity per team is easier to measure with feature teams, for sure!
upvoted 0 times
...
Josphine
8 months ago
Getting support from the business side is crucial, no doubt about it.
upvoted 0 times
...
Daniela
8 months ago
Wait, you can't do Scrum without feature teams? That sounds extreme!
upvoted 0 times
...
Tammara
8 months ago
I disagree, I think productivity might actually drop at first.
upvoted 0 times
...
Mari
8 months ago
Feature teams definitely reduce communication overhead!
upvoted 0 times
...
Anjelica
9 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?
upvoted 0 times
...
Sang
9 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.
upvoted 0 times
...
Merissa
9 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.
upvoted 0 times
...
Kati
9 months 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.
upvoted 0 times
...
Kristal
9 months 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.
upvoted 0 times
...
Anglea
9 months 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.
upvoted 0 times
...
Whitley
9 months 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.
upvoted 0 times
...
Quentin
9 months 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.
upvoted 0 times
...
Ma
9 months 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.
upvoted 0 times
...
Penney
9 months 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.
upvoted 0 times
...
Loren
10 months 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.
upvoted 0 times
...
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.
upvoted 0 times
Dalene
1 year ago
E) With feature teams, it is easier to calculate the productivity per team.
upvoted 0 times
...
Celestine
1 year ago
C) Getting support from the business side first helps.
upvoted 0 times
...
Rickie
1 year ago
A) You cannot do Scrum without feature teams.
upvoted 0 times
...
...
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.
upvoted 0 times
...
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.
upvoted 0 times
Lamar
1 year ago
D) Feature teams have less communication overhead.
upvoted 0 times
...
Karrie
1 year ago
C) Getting support from the business side first helps.
upvoted 0 times
...
Cassie
1 year ago
A) You cannot do Scrum without feature teams.
upvoted 0 times
...
...
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.
upvoted 0 times
Pok
1 year ago
D) Feature teams have less communication overhead.
upvoted 0 times
...
Kindra
1 year ago
C) Getting support from the business side first helps.
upvoted 0 times
...
Stefany
1 year ago
A) You cannot do Scrum without feature teams.
upvoted 0 times
...
...
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.
upvoted 0 times
...
Ozell
1 year ago
But won't productivity suffer if we move away from component teams?
upvoted 0 times
...
Tabetha
1 year ago
I agree, that would definitely help in the transition.
upvoted 0 times
...
Brande
1 year ago
I think we should consider getting support from the business side first.
upvoted 0 times
...

Save Cancel