최신 SAFe-RTE 무료덤프 - Scaled Agile SAFe Release Train Engineer

A. To collect team performance metrics

B. To measure the team's capacity to load ratio

C. To gauge team predictability

D. To improve quality

E. To increase predictability

A. Purchase a CI tool

B. Integrate often

C. Ensure fixing a failed integration attempt is always the top priority

D. Follow up with CI ceremonies

E. Secure senior leadership support before starting CI

F. Make integration results visible

A. lt is a Lean system engineering technique

B. lt is a team-based framework

C. lt is a set of technical software practices

D. lt is an ideal method for static design requirements

A. Key Performance Indicators (KPIs), PI Objectives, and Flow

B. PI Objectives, ART predictability measure, and KPIs

C. Outcomes, Competency, and Flow

D. ART predictability measure, SAFe outcomes, and Competency

A. Realistic

B. Rationalized

C. Random

D. Required

A. Teams have no time for fixing bugs

B. Bottlenecks can be hard to identify and resolve

C. Delivery can be blocked

D. Technical debt can grow uncontrollably

A. Praise the team for being high performers

B. Coach the team on their tendency to size Stories too small

C. Coach the team on their tendency to under-commit

D. Praise the team for being a cross-functional team

A. Agile Teams can manage daily interruptions

B. Teams are more productive than the same number of individuals

C. Changes in team composition do not impact productivity

D. Products are more robust when individuals on teams have specific skill sets

A. Iteration backlog

B. PI Objectives

C. Iteration goals

D. Program Backlog

E. Team Backlog

A. It demonstrates the need to fix the scope at the beginning of the Program Increment (PI)

B. It identifies under-performing teams

C. It focuses the Agile Release Train on predictable value delivery

D. It allows the business and other stakeholders to plan effectively

E. It indicates whether the Solution is ready to be released

A. Risks on the teams' planning boards are resolved by the Release Train Engineer

B. Draft objectives are written but do not include exploration Enablers

C. Draft objectives and uncommitted objectives are written

D. All teams' planning boards are visible and use the same color-coding

E. Teams use color-coding for their backlog items as a reminder that they are re-quired to have all backlog item types on their planning boards

A. Teams can establish face-to-face communication across all team members and stakeholders

B. Teams can review the Features and Enablers so they have an understanding of the Roadmap for the next PI

C. Teams can help support overall product integrity and facilitate working agree-merits during PI Planning

D. Teams can prepare backlogs, give feedback to the Product Owner/Product Man-agement/System Architect, and begin looking at dependencies, impediments, and knowledge building

A. Collaboration over documentation is a key recommendation of the Agile Manifes-to

B. It makes improvements actionable through backlog items for the next Program Increment

C. Workshops are more engaging than document writing

A. After PI Planning

B. During PI Planning

C. Prior to iteration planning

D. During backlog refinement

A. After every other iteration

B. After the end of each program increment (Pl)

C. After every iteration

D. After every release

A. Send them the Program Increment (PI) Objectives after each PI Planning event

B. Have them attend the Program Increment (PI) Planning event

C. Provide them a planning schedule outlining a five-year plan for development

D. Have them estimate User Stories for the teams