How does the "C" in the CALMR approach to DevOps help teams manage tensions caused by differing needs?
Correct Answer:
B
The ??C?? in the CALMR approach to DevOps stands for culture, which is the foundation of successful DevOps adoption. Culture refers to the values, beliefs, and behaviors that guide the collaboration and alignment of everyone in the value stream. By creating a culture of shared responsibility, teams can manage the tensions caused by differing needs, such as speed, quality, security, and stability. A culture of shared responsibility means that everyone is accountable for the outcomes of their work, and that they work together to deliver value to the customers. It also means that teams respect each other??s roles and expertise, and seek feedback and learning opportunities. A culture of shared responsibility fosters trust, transparency, and continuous improvement, which are essential for DevOps. References:
✑ CALMR - Scaled Agile Framework
✑ The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut
What is one way to ensure a team is holding successful Iteration Reviews and demos?
Correct Answer:
A
One way to ensure a team is holding successful iteration reviews and demos is to have the team demo working, tested system components that meet the definition of done (DoD). This shows the team??s progress and value delivery, and allows them to receive feedback from the product owner and other stakeholders. The team should minimize the use of slides and the preparation time for the demos, and focus on the solution instead of the presentation. The team should also discuss the impact of the current solution on the nonfunctional requirements (NFRs) and identify any risks or impediments.
References:
✑ Iteration Review - Scaled Agile Framework
✑ Exam Study Guide: SSM (6.0) - SAFe® Scrum Master
According to SAFe, which of the following types of work should fit into one Iteration for one team?
Correct Answer:
D
According to the SAFe 6 Scrum Master documentation, the type of work that should fit into one Iteration for one team is a Story. A Story is a short description of a small piece of functionality that provides value to the customer or stakeholder. Stories are derived from Features, which are larger units of value that typically span multiple Iterations. Stories are also decomposed into Tasks, which are the specific activities that the team members perform to implement the Story. Stories are the primary backlog items that the team plans, estimates, and delivers in an Iteration. They are also the basis for defining and committing to the Iteration goals. Stories should be small enough to be completed within one Iteration, and they should meet the definition of ready and the definition of done. (Must be taken from SAFe 6 Scrum Master resources)
References:
✑ Stories
✑ Features
✑ Tasks
✑ Iteration Planning
What is one trait of a servant leader?
Correct Answer:
A
According to the SAFe 6 Scrum Master documentation, one of the traits of a servant leader is to persuade rather than use authority. This means that the servant leader influences others by appealing to their values, beliefs, and interests, rather than by imposing their own will or position. By persuading rather than using authority, the servant leader fosters a culture of collaboration, empowerment, and trust, where team members are more likely to accept and welcome coaching, feedback, and change. Persuasion also helps the servant leader to align the team with the organization??s vision, mission, and goals, and to create a shared understanding of the purpose and value of the work. (Must be taken from SAFe 6 Scrum Master resources)
References:
✑ Scrum Master/Team Coach
✑ Servant Leadership: A Key Driver of High-Performing Agile Teams
✑ The Scrum Master as a Servant-Leader
