최신 SAFe-SPC 무료덤프 - Scaled Agile SAFe Practice Consultant SPC (6.0)

A. Capability is a different name for Features, one that is preferred by some organizations.

B. Capabilities are simply a level of abstraction above Epics, exhibiting largely the same characteristics and practices.

C. Capabilities are simply a different kind of Epic, exhibiting largely the same characteristics and practices.

D. Capabilities are simply a level of abstraction above Features, exhibiting largely the same characteristics and practices.

A. Customer collaboration over contract negotiation.

B. Continuous attention to technical excellence and design enhances agility.

C. Working software over comprehensive documentation.

D. Good architectures are built up front so that teams can focus on development.

E. Business people and developers must work together daily throughout the project.

F. Working software is the primary measure of progress.

A. 80-100%

B. <50%

C. None of the above.

D. 100%

E. 50-75%

A. Team Iteration Demo

B. Roadmap update

C. Iteration Metrics update

D. PI Predictability Measure update.

E. Biweekly System Demo

A. Preserve flexibility in both system functionality and design.

B. Preserve flexibility in system functionality and design, but have fixed Solution intent.

C. Assume variability of scope and preserve options for the release date.

D. Assume variability of scope, but have fixed Solution Context.

A. After every Iteration.

B. After continuous integration.

C. After Pre-PI Planning.

D. After the Solution Demo, but before PI Planning.

E. On demand.

A. It increases engagement and focuses everyone all at once with purpose and intent

B. It makes it much clearer to stakeholders that waterfall is not a good investment

C. It allows the teams to reinforce their knowledge by attending SAFe for Teams the day after PI Planning

D. It reduces the number of Scrum Masters/Team Coaches required to support the teams

A. If something goes wrong with the production environment, teams can switch their staging to perform the role of production.

B. It allows the System Team to test the deployability of the Solution.

C. It enables SAFe teams to Develop on Cadence and Release Any Time.

D. Teams can verify whether new functionality or Nonfunctional Requirements are compatible with the current production configuration.