New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum PSM-II Exam - Topic 4 Question 77 Discussion

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

Which way of creating Scrum Teams is consistent with the Scrum values?

(choose the best answer)

Show Suggested Answer Hide Answer
Suggested Answer: A, C

According to the Large-Scale Scrum (LeSS) framework, one of the principles for scaling agile development is to descale the organization, which means simplifying the structure and reducing dependencies and handoffs. A well-structured Product Backlog can help achieve this by enabling feature teams, which are cross-functional and cross-component teams that can deliver a complete customer-centric feature. Feature teams minimize and often eliminate Developers working on multiple Scrum Teams during a Sprint, as they can focus on one Product Backlog item at a time. This also improves productivity, quality, and learning, as Developers can avoid context switching and multitasking, which are known to reduce efficiency and effectiveness. A person working on multiple Scrum Teams at the same time is often less productive than when that person can focus on the Sprint Backlog of a single Scrum Team.

The Large-Scale Scrum (LeSS) framework also states that Scrum does not change when scaling up to multiple teams. The core Scrum framework remains intact, with one Product Owner, one Product Backlog, and potentially releasable Increments every Sprint. The only changes are adding a few coordination practices to cope with the increased complexity and interdependencies. Therefore, changes to the core Scrum framework are not needed to be successful with Scrum at large scale.

Scrum Team members do not have to be working full time on a team, as long as they are committed to the Sprint Goal and deliver a Done Increment every Sprint. However, it is recommended that they spend as much time as possible with their team, as this fosters collaboration, communication, and alignment.


The Large-Scale Scrum (LeSS) framework | Atlassian, accessed on September 30, 2023

Overview - Large Scale Scrum (LeSS), accessed on September 30, 2023

Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum, Craig Larman and Bas Vodde, 2010

Leading Large Scale Product Development with Large-Scale Scrum (LeSS), Kamlesh Ravlani, 2015

Contribute your Thoughts:

0/2000 characters
Lonny
3 months ago
I agree, A promotes self-organization which is key!
upvoted 0 times
...
Gregg
3 months ago
Wait, can a Chief Product Owner really decide team structures?
upvoted 0 times
...
Tasia
3 months ago
C sounds way too top-down for Scrum values.
upvoted 0 times
...
Rebbecca
4 months ago
I think B makes more sense for team dynamics.
upvoted 0 times
...
Shelia
4 months ago
A is definitely the way to go!
upvoted 0 times
...
Davida
4 months ago
I’m a bit confused. I thought managers assigning people, like in B, could work if they collaborate well, but it doesn’t feel very Scrum-like.
upvoted 0 times
...
Gilma
4 months ago
I think we practiced a question similar to this, and it emphasized the importance of collaboration and self-organization. A seems to align with that.
upvoted 0 times
...
Carolynn
4 months ago
I'm not entirely sure, but I feel like assigning people to teams based on skills, like in option C, goes against the idea of team autonomy.
upvoted 0 times
...
Regenia
5 months ago
I remember discussing how Scrum values self-organization, so I think option A might be the right choice.
upvoted 0 times
...
Gracie
5 months ago
I'm leaning towards B, but I'll double-check the Scrum framework to make sure I'm not missing anything.
upvoted 0 times
...
Ressie
5 months ago
Option C doesn't seem quite right. The Scrum Guide emphasizes self-organization, so I don't think the Chief Product Owner should be dictating the team structure.
upvoted 0 times
...
Sue
5 months ago
I've got a good feeling about option A. Providing boundaries for the team to self-organize seems to fit the Scrum values of empowerment and collaboration.
upvoted 0 times
...
Alexia
5 months ago
Hmm, I'm a bit confused. I'll need to review the Scrum principles to figure out which option aligns best.
upvoted 0 times
...
Queen
5 months ago
This is a tricky one. I'll need to think carefully about the Scrum values to determine the best approach.
upvoted 0 times
...
Natalie
10 months ago
B has 'manager' written all over it. That's the antithesis of what Scrum is trying to achieve.
upvoted 0 times
Basilia
9 months ago
C) The Chief Product Owner determines the team structures and assigns who is needed in which Scrum Team based on skills, seniority and the business area.
upvoted 0 times
...
Roy
10 months ago
B) Managers collaborating across their respective areas of responsibility to assign individuals to specific teams.
upvoted 0 times
...
Florinda
10 months ago
A) Providing boundaries that help the team members organize themselves into Scrum Teams.
upvoted 0 times
...
...
Mignon
10 months ago
Haha, C sounds like a recipe for disaster. The Chief Product Owner isn't the Scrum Master, you know!
upvoted 0 times
Melita
8 months ago
A) Providing boundaries that help the team members organize themselves into Scrum Teams.
upvoted 0 times
...
Thomasena
8 months ago
Haha, C sounds like a recipe for disaster. The Chief Product Owner isn't the Scrum Master, you know!
upvoted 0 times
...
Florencia
9 months ago
B) Managers collaborating across their respective areas of responsibility to assign individuals to specific teams.
upvoted 0 times
...
Moira
9 months ago
A) Providing boundaries that help the team members organize themselves into Scrum Teams.
upvoted 0 times
...
...
Georgeanna
10 months ago
I disagree. Option C seems more efficient to me as it ensures the right skills are in each team.
upvoted 0 times
...
Antione
11 months ago
I'd go with A as well. Scrum is all about empowering the team, not dictating from the top down.
upvoted 0 times
Kallie
10 months ago
I agree, empowering the team is key in Scrum.
upvoted 0 times
...
Glory
10 months ago
A) Providing boundaries that help the team members organize themselves into Scrum Teams.
upvoted 0 times
...
...
Francoise
11 months ago
I agree with Leonor. Giving boundaries for self-organization is key in Scrum.
upvoted 0 times
...
Justa
11 months ago
Option A seems to encourage self-organization, which is a key Scrum value. The other options sound more like traditional management approaches.
upvoted 0 times
Fabiola
9 months ago
Option A seems to encourage self-organization, which is a key Scrum value.
upvoted 0 times
...
Erick
9 months ago
C) The Chief Product Owner determines the team structures and assigns who is needed in which Scrum Team based on skills, seniority and the business area.
upvoted 0 times
...
Tess
9 months ago
B) Managers collaborating across their respective areas of responsibility to assign individuals to specific teams.
upvoted 0 times
...
Leoma
10 months ago
A) Providing boundaries that help the team members organize themselves into Scrum Teams.
upvoted 0 times
...
...
Leonor
11 months ago
I think option A is the best way to create Scrum Teams.
upvoted 0 times
...

Save Cancel