Complete SAFe-Practitioner Scrum Materials

In SAFe 6.0, during PI Planning, program risks are identified, categorized, and addressed in a process called the ROAM technique. ROAM stands for Resolved, Owned, Accepted, and Mitigated.

Resolved means the risk has been addressed and is no longer a concern.

Owned means someone takes responsibility for managing the risk.

Accepted means the risk is acknowledged and will be monitored.

Mitigated means steps are taken to reduce the impact or likelihood of the risk.

Thus, the correct category that addresses potential risks is Resolved (option A).

 = WIP limits are necessary in the ART Kanban to ensure large queues are not forming, which would slow down the flow of value and increase the lead time. WIP limits are a way of applying the Lean principle of reducing waste and optimizing the system for the whole. By limiting the amount of work that can be in progress at any stage of the Kanban system, the ART can balance the demand and capacity, avoid overloading the system, and focus on completing the work rather than starting new work. WIP limits also help to expose bottlenecks, dependencies, and impediments that need to be resolved to improve the flow efficiency and quality of the work. References: = ART Flow - Scaled Agile Framework, ART and Solution Train Backlogs - Scaled Agile Framework, Kanban And The Importance Of Work In Progress (WIP) Limits

 According to the SAFe Implementation Roadmap, culture change is the last step in the transformation process. It states that “culture change comes last, not first. You can’t change a culture until you have changed the underlying behavior and the results that the behavior produces” 1. Therefore, the best way to change the culture is to adopt new approaches that deliver better outcomes and then anchor them in the culture by reinforcing the benefits and values they bring. This is consistent with Kotter’s model of leading change, which also suggests that anchoring new approaches in the culture is the final stage of a successful change effort 23. References: Enhance the Portfolio, Leading Change (Step 8) – Anchor Change in the Culture, Anchor Change in Your Organization’s Culture

Refactoring is the process of improving the design and structure of existing code without changing its external behavior. It is a quality practice for software development because it helps to reduce technical debt, improve maintainability, readability, and testability, and enable faster delivery of value. Refactoring is one of the core engineering practices in SAFe, along with Test-First, Continuous Integration, and Pair Work. References: SAFe for Teams - Know Your Role on an Agile Team, Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe for Teams | SAFe Practitioner (SP) Certification, Built-in Quality