What is one way a servant leader can support team members in decision-making?
Correct Answer:A
According to the SAFe 6 Scrum Master documentation, one of the ways a servant leader can support team members in decision-making is by giving each team member the opportunity to contribute. This means that the servant leader encourages and facilitates the participation of all team members in the decision-making process, ensuring that everyone??s voice is heard and valued. By giving each team member the opportunity to contribute, the servant leader fosters a culture of collaboration, empowerment, and trust, as well as increases the quality and buy-in of the decisions. (Must be taken from SAFe 6 Scrum Master resources)
References:
✑ Scrum Master/Team Coach
✑ The Power of Shared Decision-Making through Servant-Leadership
✑ The Scrum Master as a Servant-Leader
What is one example of an Agile Team development practice?
Correct Answer:C
One example of an Agile Team development practice is to demo working functionality frequently to the product owner and other stakeholders. This practice helps the team to get fast feedback, validate their assumptions, and ensure that they are delivering value that meets the customer needs and expectations. Demoing frequently also helps the team to improve the quality of their work, as they have to ensure that the functionality is tested and meets the definition of done before showing it to others. Demoing frequently is part of the SAFe Scrum and SAFe Team Kanban practices, and is done at the end of each iteration in the Iteration Review event.
References:
✑ Iteration Review - Scaled Agile Framework
✑ SAFe Team Kanban - Scaled Agile Framework
✑ Agile Teams - Scaled Agile Framework
During which of the following Agile Team events do team members estimate relative story sizes?
Correct Answer:A
Backlog Refinement is the Agile Team event where team members estimate relative story sizes. Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable,and small enough to be completed in a single iteration2 To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3 Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4 The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35 (Must be taken from SAFe 6 Scrum Master resources) References:
✑ Team Backlog - Scaled Agile Framework
✑ Backlog Refinement - Scaled Agile Framework
✑ Story - Scaled Agile Framework
✑ How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog
✑ Why Your Agile Team Should Use Relative Story Point Estimation
What is the intended value of the Backlog Refinement event?
Correct Answer:A
The intended value of the Backlog Refinement event is that the team is able to prepare requirements for Iteration Planning. Backlog Refinement is an ongoing process where theteam collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single Iteration2 By doing so, the team can improve the quality, efficiency, and effectiveness of their work, as well as deliver value to the customers and the organization123 References:
✑ Team Backlog - Scaled Agile Framework
✑ Backlog Refinement - Scaled Agile Framework
✑ What is backlog refinement? | Miro
Who are important attendees to the PI System Demo?
Correct Answer:C
According to the SAFe 6 Scrum Master documentation, one of the important attendees to the PI System Demo is the Business Owners. Business Owners are a small group of stakeholders who have the primary business and technical responsibility for governance, compliance, and return on investment (ROI) for a Solution developed by an Agile Release Train (ART). They are key stakeholders on the ART who must evaluate fitness for use and actively participate in certain ART events. The PI System Demo provides them an opportunity to see the integrated view of new features delivered by the ART, give feedback, and influence the future direction of the solution. (Must be taken from SAFe 6 Scrum Master resources)
References:
✑ System Demo
✑ [Business Owners]
What is one element on the Scrum Master/Team Coach responsibility wheel?
Correct Answer:B
According to the SAFe 6 Scrum Master documentation, one of the elements on the Scrum Master/Team Coach responsibility wheel is to facilitate PI Planning. PI Planning is a two- day event where all the teams and stakeholders of an Agile Release Train (ART) collaborate to align on a common vision, define and commit to the PI objectives, and
identify and manage risks and dependencies. The Scrum Master/Team Coach facilitates PI Planning by 1:
✑ Helping the team prepare for the event, such as reviewing the business context,
vision, and backlog, and creating draft plans
✑ Supporting the team during the event, such as facilitating breakout sessions, resolving issues, and ensuring alignment and collaboration with other teams
✑ Assisting the team after the event, such as finalizing the plans, updating the PI board, and conducting a retrospective
Facilitating PI Planning is one of the ways the Scrum Master/Team Coach helps the team and the ART achieve their goals and deliver value. (Must be taken from SAFe 6 Scrum Master resources)
References:
✑ PI Planning
✑ Scrum Master/Team Coach
✑ Say Hello to SAFe 6.0! - Scaled Agile Framework