Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum Exam PSM-II Topic 4 Question 66 Discussion

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

Which two statements are true regarding the nature of large-scale product development with Scrum?

(choose the best two answers)

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:

Margurite
12 months ago
So, we all agree on A and C? Minimizing multitasking and a good backlog sound like key factors for large-scale Scrum.
upvoted 0 times
...
Tabetha
1 years ago
I’m with Claire and Daniel. A and C seem to be the correct options. Full-time work per team might not always be feasible.
upvoted 0 times
...
Wilda
1 years ago
I agree. A and C are solid. B is tricky; modifying the core framework usually isn't recommended.
upvoted 0 times
...
Louvenia
1 years ago
I think A and C make sense. A structured backlog and focused team members boost productivity.
upvoted 0 times
...
Yuki
1 years ago
Yeah, the one about Scrum. What are you leaning towards?
upvoted 0 times
...
Johnson
1 years ago
Has anyone else thought about the large-scale product dev question?
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77