11. Which SAFe Principle is being applied when a Release Train Engineer treats Suppliers as partners?
a) Build incrementally with fast, integrated learning cycles
b) Assume variability; preserve options
c) Decentralize decision-making
d) Apply systems thinking
12. Which three SAFe constructs create business alignment across the Agile Release Train? (Choose three.)
a) Enablers
b) Communities of practice
c) Roadmap
d) Epics
e) Vision
f) Program Backlog
13. During Program Increment (PI) Planning, a scrum of scrums is occurring just before the draft plan review. The Scrum Master of one team states that one of the Product Managers just showed up to their planning area with a priority wish list of items.
The items do not align with the Feature prioritization. What is the most likely planning anti-pattern causing this sudden impediment?
a) Prioritization by Product Management was performed autonomously not collaboratively
b) Planning decisions have been centralized
c) There is strong alignment between business and marketing
d) There is no social network that Solution development relies on
14. What are two responsibilities of the Release Train Engineer as chief Scrum Master for the Agile Release Train (ART)? (Choose two.)
a) Escalate ART impediments
b) Break down Features into Stories
c) Analyze Epics in the Portfolio Kanban
d) Facilitate Program Increment (PI) Planning
e) Provide the go/no-go decision for large initiatives
15. There is great interest in the Agile Release Train's progress, and the Release Train Engineer (RTE) has been asked to attend multiple reviews and status meetings to discuss progress at the end of each Iteration.
What action could the RTE take to manage expectations?
a) Encourage interested parties to attend the System Demo
b) Determine the RTE's capacity for attending meetings and do not exceed it
c) Make status available at the end of every other Iteration rather than every Iteration
d) Delegate some program reporting and meeting attendance to Scrum Masters on the train
16. During Program Increment (PI) execution, the System Team is unclear about how to test some of the larger Features. What should a Release Train Engineer do?
a) Escalate the problem to senior management to get the required action
b) Allow the problem to reach a critical point knowing that a minor failure is a technique for learning
c) Direct Product Management to define the use cases for the Features
d) Encourage the System Team and Product Management to meet and collaborate on a solution
17. Which core competency best describes the critical skills of Scrum, Kanban, and the Built-in Quality practices that are needed to manage the flow of value?
a) Lean Portfolio Management
b) Agile Product Delivery
c) Team and Technical Agility
d) Enterprise Solution Delivery
18. What steps can a Release Train Engineer (RTE) take to promote facilitation support for a distributed Program Increment (PI) Planning event?
a) Align and arrange a local RTE-proxy and technical support person at each location to join for all pre-event preparation sessions and the PI Planning event itself
b) Split up the PI Planning event by location and have a local RTE focus on the local PI Objectives
c) During the Innovation and Planning (IP) Iteration, ask a Scrum Master at the other location to facilitate the PI Planning event locally
d) Arrange and test audio and video connectivity multiple times so participants can always hear and see the RTE
19. Teams are reporting a high level of success through their individual quantitative measurements, but the system results say otherwise. What should the Release Train Engineer do to help the teams deliver more value?
a) Diagnose the differences between the measurements and the results and suggest improvement items to each team
b) Share the quantitative measurement results with Product Management and leadership and ask for their input
c) Work with the team that is struggling the most to discover patterns that can be applied to the other teams
d) Coach the Scrum Masters on good retrospective techniques and ensure teams are defining and taking a systems view approach to improvements