You are the Scrum Master of a Scrum Team that has one Developer who disagrees with team decisions. Their disagreements are becoming disruptive and slowing progress. The Developer often returns to earlier team decisions and re-opens the issue.
What are two ways to go about this problem?
(choose the best two answers)
A: You organize an offsite team building activity to establish a foundation of trust. You observe whether the problem persists after the offsite activity. This is a good way to foster a positive team culture and improve the relationships among the team members. The offsite activity can help the team to have fun, relax, and bond with each other. It can also create an opportunity for the team to discuss their issues and concerns in a more informal and friendly setting. The Scrum Master can observe whether the problem of disagreement is resolved or reduced after the offsite activity, and provide feedback and support as needed.
E: To every team member expressing this concern you suggest raising this with the full team. You offer to help initiate the conversation but not to resolve the concern yourself. This is a good way to empower the team to address their own problems and find their own solutions. The Scrum Master can encourage the team members to speak up and share their perspectives and feelings with the whole team, rather than keeping them to themselves or complaining to others. The Scrum Master can also facilitate the conversation and ensure that it is respectful, constructive, and productive, but not intervene or impose their own opinion or decision.
Scrum Guide 2020, page 13: ''The Scrum Master serves the Scrum Team in several ways, including coaching the team members in self-management and cross-functionality.''
Professional Scrum Master II Course, page 20: ''The Scrum Master can help the team to build trust by creating a safe environment where people can express themselves openly and honestly, without fear of judgment or retaliation.''
Professional Scrum Master II Course, page 21: ''The Scrum Master can help the team to resolve conflicts by facilitating dialogue, listening actively, asking powerful questions, and supporting collaborative decision making.''
You are the Scrum Master for four Scrum Teams working from the same Product Backlog. Several of the Developers come to you complaining that work identified for the upcoming two Sprints will require full time commitment from Stella, an external specialist who is not a member of any of the four Scrum Teams. What would you consider acceptable solutions for the problem?
(choose the best three answers)
B) Developers with an interest in Stella's domain could volunteer to take on this work in their respective Scrum Teams.
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
Scrum requires a Definition of Done. Which phrases describe the purpose of the Definition of Done?
(Select the best three answers)
The Definition of Done is a formal description of the state of the Increment when it meets the quality standards required for the product. The purpose of the Definition of Done is to:
During the Sprint, it helps the Developers identify the work remaining for an Increment to be ready for release by the end of a Sprint (B), by providing a clear and shared understanding of what ''Done'' means for each Product Backlog item and the Increment as a whole.
It creates transparency into the state of the Increment when it is inspected at the Sprint Review , by ensuring that everyone involved in the product development has the same expectations and criteria for evaluating the value, usability, and quality of the Increment.
It guides the Developers when creating a forecast at the Sprint Planning (D), by enabling them to estimate how much work they can realistically complete within a Sprint, based on their capacity, skills, and Definition of Done.
What can the Scrum Value of openness easily impact?
(choose the best answer)
The Scrum Value of openness can easily impact all of the aspects listed in the question. Openness means that the Scrum Team and the stakeholders agree to be transparent about their work, their challenges, their learnings, and their progress. This fosters a culture of collaboration, trust, feedback, and continuous improvement. Openness also helps to ensure that the product quality meets the expectations of the customers and the stakeholders, and that the product is delivered in a timely manner. Openness also contributes to employee satisfaction, as it allows the Scrum Team members to express their opinions, share their ideas, and learn from each other.
The Scrum Guide, section 2.2 (Scrum Values), page 6
The Scrum Master Learning Path, module 1 (Scrum Theory), lesson 3 (Scrum Values)
Brett
3 days agoLisbeth
11 days agoMicaela
18 days agoLeah
25 days agoWilburn
1 month agoLizbeth
1 month agoLizette
2 months agoHerminia
2 months agoJutta
2 months agoKami
2 months agoJoni
3 months agoCarrol
3 months agoMyrtie
3 months agoMaxima
3 months agoDonte
4 months agoTyra
4 months agoRoy
4 months agoAngelyn
4 months agoNathalie
5 months agoDorothy
5 months agoAdelle
5 months agoDenise
5 months agoGladis
6 months agoLili
6 months agoKiera
6 months agoHillary
6 months agoPamella
7 months agoHelga
7 months agoNoah
7 months agoMarge
9 months agoBelen
10 months agoCarmela
11 months agoRodrigo
1 year agoFabiola
1 year agoJacquelyne
1 year agoAretha
1 year agoTammara
1 year agoLorenza
1 year agoDelsie
1 year agoOlive
1 year agoAudra
1 year agoJanae
1 year agoJess
1 year agoCristen
2 years agoTricia
2 years agoYesenia
2 years agoJoni
2 years agoJustine
2 years agoMicah
2 years agoLashawn
2 years agoMi
2 years agoGene
2 years agoIlene
2 years agoAlethea
2 years agoIsadora
2 years ago