최신 SP-SAFe-Practitioner 무료덤프 - Scaled Agile SAFe for Teams SP (6.0) - SAFe Practitioner

A. During the quantitative part of the team retrospective

B. During the time and materials retrospective

C. During the Features agreement retrospective

D. During the qualitative part of the team retrospective

A. Significant dependencies

B. Epics

C. Capacity and load

D. Risks

A. Visibility into analysis, approval, and Feature readiness for implementation

B. Visibility into backlog items

C. Visibility into program Epics and Features

D. Visibility into scope and priority adjustments

A. Release on Demand

B. Continuous Integration

C. Continuous Exploration

D. Continuous Deployment

A. Total wait time + Flow time [Total wait time plus Flow time]

B. Total active time + Flow time [Total active time plus Flow time]

C. Total active time / Flow time [Total active time divided by Flow time]

D. Total wait time / Flow time [Total wait time divided by Flow time]

A. As many team members as possible should attend remotely to reduce travel costs

B. It is not a required event but tasks move forward at higher velocity when the meeting occurs

C. It is an all-hands, two-day event with the goal to create alignment

D. It is very important and should be postponed until all participants can attend

A. Keep everything under version control

B. Build cross-functional Agile Release Trains around the flow of value to the Customer

C. Decentralize decision making

D. Establish a work environment of shared responsibility

A. Executive roles

B. Developer roles

C. Product roles

D. Architecture roles

A. Determining velocity is a new function in each Iteration; previous Iterations should not be ^ transferred to a new Iteration

B. The team members assess their availability, acknowledging time off and other potential v u duties

C. Identify work on technical infrastructure, tooling, and other systemic impediments

D. Maintenance tasks do not need to be included in velocity; maintenance tasks fall outside thi scope

A. The Management Review and Problem-Solving workshop

B. The second team breakout session

C. The draft plan review

D. The final plan review

A. Make value flow without interruptions

B. Build incrementally with fast, integrated learning cycles

C. Organize around value

D. Take an economic view

A. Centralize decision-making

B. Reduce work in process (WIP) limits

C. Strive to achieve a state of continuous flow

D. Provide autonomy

A. To gain the fastest velocity with well defined interfaces

B. To create each replaceable component with minimized dependencies

C. To obtain high reuse and technical specialization with a focus on nonfunctional requirements

D. To develop T-shaped skills together with Continuous Integration

A. Program-level risks

B. Each teams tasks

C. Dependencies between teams

D. Work breakdowns

A. Improves transparency

B. Removes accountability from leaders

C. Reduces delays

D. Ensures strategic decisions are made collaboratively

A. Move testing and validation activities earlier in the work cycle to get faster or continuous feedback

B. Perform testing and validation activities in the production environment under real-world conditions

C. Run two nearly identical production environments, moving users between the two to make small changes to one or the other

D. Write tests at the end of development to capture potential failures discovered throughout the development process

A. Relentless improvement

B. Support organizational change

C. Mindset and Principles

D. Emotional Intelligence