SAFe-RTE 無料問題集「Scaled Agile SAFe Release Train Engineer」

（A）Allow the teams as much flexibility as possible to promote innovation

（B）Work with development leaders to make sure they give clear and detailed guid-ance to the developers on what is expected

（C）Get approval for work to be done in the hackathon

（D）Ensure the teams have allocated story points in the Innovation and Planning Itera-tion during the Program Increment to account for the effort

（A）To align the team members and the Product Owner to the mission

（B）To hold the team accountable to their Pl Objectives

（C）To summarize the business outcomes an Agile Team intends to achieve during the Program Increment (PI)

（A）Pareto analysis

（B）Fishbone diagram

（C）Modified Fibonacci

（D）Dot voting

（A）Address and resolve any problems areas

（B）Survey full-time employees

（C）Conduct an employee Net Promoter Score (NPS) survey

（D）Gather employee metrics immediately after the ART launches

（A）Feature delivery

（B）Business Value assignment

（C）Problem-solving

（D）ART predictability

（A）It is a combination of PO-sync and Scrum of Scrums events

（B）It occurs during the Innovation and Planning iteration

（C）It is run after PO-sync and Scrum of Scrum events

（D）Attendance by the entire ART is important

（A）Run the meeting in front of the program board

（B）Facilitate the meeting using a focused and visible agenda and timebox

（C）Review individual team performance

（D）Address the most important questions for Program Increment (PI) execution

（A）Encourage continuous learning

（B）Ensure time is allocated for innovation and planning

（C）Provide a team vision

（D）Encourage skill specialization

（E）Facilitate conflict

（A）Ask the teams to commit only to Enablers as their PI Objectives during the PI Planning and address Features as uncommitted objectives for the first PI

（B）Ask the Business Owner which Enablers have high business value

（C）Work with Product Management and System Architects to identify future Features and determine the Enablers to achieve them

（D）Create alignment with the System Architect and Product Management that the first PI is all about Enablers to plan for creating business value in the second PI

（A）Facilitate Product Management and other stakeholders in prioritization of the Pro-gram Backlog

（B）Ensure that at least 30% of the Program Backlog is allocated to Enabler Features

（C）Allocate time in the scrum of scrums meeting for Product Management to social-ize with the teams the Features for the upcoming PI

（D）Provide approval and sign-off for draft Team Backlogs

（A）Problem-solving workshop

（B）Team Iteration plans

（C）Draft objectives

（D）ROAMing Risks

（A）Ask the Business Owner which Enablers have high business value

（B）Ask the teams to commit only to Enablers as their Program Increment (PI) Objec-tives during the PI Planning event and address Features as uncommitted objec-tives for the first PI

（C）Work with Product Management and System Architects to identify future Features and determine the Enablers to achieve them

（D）Create alignment with the System Architect and Product Management that the first Program Increment (PI) is all about Enablers in order to plan for creating business value in the second PI

（A）Establishing an architectural vision for the Agile Release Release Train

（B）Defining Program Backlog content

（C）Prioritizing the Portfolio Backlog

（A）To escalate and track impediments

（B）To facilitate the System Demo

（C）To direct the management of the communities of practice

（D）To make decisions on resource issues for critical bottlenecks

（E）To formulate and direct decisions on risks

（A）Launch Agile Release Trains

（B）Determine Epic job size using the Lean business case

（C）Implement the Lean Portfolio Management core competency

（D）Coordinate all Agile Release Trains to provide feedback for cost of delay factors

（A）Looking out for the interests of customers and stakeholders

（B）Ensuring appropriate justice is served if things go wrong

（C）Creating an environment of mutual influence

（D）Protecting the teams and train from negative reviews

（A）That it has dependencies on teams in other Agile release trains (ARTs) or Solution Trains

（B）That the team has been assigned, but the feature' uependencies have not been identified yet

（C）That the feature can be completed by that team independently

（D）That the team has not broken the feature into stories yet and has not identified dependencies

（A）Overall train velocity goes up and the time-to-market goes down

（B）It substantially decreases the predictability of the Solution Intent

（C）It reduces the overall predictability established through cadence and synchroniza-tion

（D）It decreases job satisfaction by removing autonomy and purpose

（A）Cumulative flow diagram

（B）Team status report

（C）System Demo

（D）Scrum of scrums