Which two statements are true regarding the nature of large-scale product development with Scrum?
(choose the best two answers)
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
Leading Large Scale Product Development with Large-Scale Scrum (LeSS), Kamlesh Ravlani, 2015
You are a Scrum Master employed by the IT department. The IT manager considers adopting Scrum tor a new project He wonders however, what the value is in having all team members attend this meeting called "Daily Scrum" every day. The organization already has its employees attending so many mandatory meetings.
What are two outcomes of the Daily Scrum you inform him about, to express the importance of the Daily Scrum?
(choose the best two answers)
The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is not a status meeting, but a way for the Developers to collaborate and self-organize around the most important work for the next 24 hours. The Daily Scrum also provides an opportunity for the Developers to identify and communicate any impediments that are hindering their progress, and request help from the Scrum Master or other team members to resolve them.
What is a Daily Scrum? | Scrum.org
What Is the Daily Scrum? | A Guide to the Daily Event - Scrum Alliance
What is the primary concern when multiple Scrum Teams work from the same Product Backlog with the goal of creating a valuable and useful integrated Increment by the end of their Sprint?
(choose the best answer)
What is one way to determine if the Product Owner is interacting with the Developers enough throughout a Sprint?
(choose the best answer)
A. The Developers should determine the percentage of time the Product Owner is required to be present and monitor whether the Product Owner's average presence is around this figure.
Some reasons why the other options are not correct are:
C: Observe whether the Developers need to ask the Product Owner questions at times other than during the Daily Scrum. This option is not correct because it implies that asking questions is a sign of insufficient interaction, which may not be true. Asking questions is a natural and healthy part of communication and collaboration between the Product Owner and the Developers. It shows that they are engaged, curious, and willing to learn from each other. It also helps them to clarify requirements, expectations, and feedback, and to resolve any ambiguities or conflicts. Asking questions does not necessarily mean that there is a lack of interaction, but rather that there is a need for more information or clarification.
What is an Increment? | Scrum.org
What Is a Daily Standup? | A Guide to Running Effective Standup Meetings | Atlassian
What is the primary concern when multiple Scrum Teams work from the same Product Backlog with the goal of creating a valuable and useful integrated Increment by the end of their Sprint?
(choose the best answer)
Currently there are no comments in this discussion, be the first to comment!