A.  

Combine multiple stories into larger stories

B.  

Push defects to the Innovation and Planning (IP) Iteration

C.  

Facilitate backlog refinement of the current iteration

D.  

Communicate potential missed goals or objectives as early as possible

A.  

Healthy interactions over detailed plans

B.  

Customer collaboration over contract negotiation

C.  

Risk-taking over process development

D.  

Working teams over busy individuals

A.  

Generating innovative approaches to common issues facing teams and ARTs

B.  

Forming working groups to better understand issues from the PI

C.  

Creating improvement backlog items as planned work

D.  

Developing solutions to recognized problems that blocked or slowed work

A.  

Implement a formal complaints system

B.  

Encourage team members to resolve conflicts on their own

C.  

Enforce working agreements

D.  

Escalate conflicts to the Release Train Engineer

A.  

By reviewing its processes before the next iteration

B.  

By committing to a set of goals to be delivered

C.  

By agreeing on a meeting timebox

D.  

By sharing Stories that could be pairing opportunities

A.  

Ensure subject matter experts are invited

B.  

Create a reusable agenda for the team ahead of time

C.  

Generate ideas for Stories with the team before refinement

D.  

Assure teammates that they will be heard

A.  

By reviewing goals and reflecting on what did not happen according to plan

B.  

By writing improvement Stories

C.  

By reviewing team metrics

D.  

By discussing completed work

A.  

Board Members

B.  

Feature Owners

C.  

Business Owners

D.  

Portfolio Management

A.  

Healthy conflict

B.  

Mutual trust

C.  

Effective decision-making

D.  

Clear goals and purpose

A.  

They could lose an opportunity to build relationships across the teams

B.  

They could lose an opportunity to manage risks and communication within the ART

C.  

They could lose an opportunity to collaborate with other developers and understand dependencies

D.  

They could lose an opportunity to consider new approaches to Solution delivery

A.  

Challenges between teams that design functionality and those that test the functionality

B.  

Challenges between teams that build Solutions and those who operate the Solutions

C.  

Challenges between teams that deploy products and those that collect customer feedback

D.  

Challenges between teams that talk with customers daily and those that meet with customers for research

A.  

Individual team members could lose an opportunity to learn from one another

B.  

Individual team members could lose an opportunity to keep their technical skills current

C.  

Individual team members could lose an opportunity to consider their team work more holistically

D.  

Individual team members could lose an opportunity to refresh their motivation

A.  

Identify as many risks and dependencies as possible for the management review

B.  

Align on how the team will answer questions about their proposed objectives

C.  

Secure support from other teams on how work will be shared and completed

D.  

Ensure the team has Stories written for the first two Iterations of the increment

A.  

Features

B.  

Epics

C.  

Tasks

D.  

Stories

A.  

Too many teams present Enablers and technical debt

B.  

Product Managers lead the problem-solving workshop

C.  

Product Owners present all of the work in the PI System Demo

D.  

Not enough preparation goes into the quantitative and qualitative measurement section

A.  

They do not invite people outside of the team

B.  

They focus only on what to improve and not what to preserve

C.  

They focus mostly on problems within the team's control

D.  

They do not vote on action items

A.  

Flow time is decreasing

B.  

Capacity and load are exactly the same

C.  

Team members are pulling in work from future Iterations

D.  

Team velocity increases over time

A.  

PO Sync

B.  

System Sync

C.  

Coach Sync

D.  

Product Sync

A.  

To identify what to present in System Demo

B.  

To communicate which Stories will be completed during the Iteration

C.  

To align team members to common objectives

D.  

To get feedback from the organization

A.  

The team can do team building activities

B.  

The team can allocate time for vacation

C.  

The team can take time for personal appointments

D.  

The team can prepare for PI planning

A.  

Encourage team members to acquire T-shaped skills

B.  

Suppress team conflicts to encourage more productivity

C.  

Assign Stories so the team does not have to pull from the Kanban

D.  

Encourage handoffs to allow each team member to contribute

A.  

Give each team member the opportunity to contribute

B.  

Perform regular retrospectives on behalf of the team

C.  

Identify solutions to problems the team surfaces

D.  

Support teams in affinity mapping their concerns

A.  

They ensure the team has additional development options

B.  

They generate additional ways to measure team progress

C.  

They create an opportunity for teams to take on harder work

D.  

They maintain the predictability of achieving the objectives

A.  

Patience

B.  

Openness

C.  

Commitment

D.  

Communication

A.  

It provides dedicated time for innovation and continuing education

B.  

It provides committed time for more team communication

C.  

It provides time for teams to take vacation

D.  

It provides focused time for teams to complete quality testing

A.  

Ability to support customer communications regularly

B.  

Ability to efficiently share designs with contributors

C.  

Ability to deliver value to customers earlier

D.  

Ability to easily manage requirements across teams

A.  

Prioritization across all backlogs

B.  

Facilitation techniques amongst all meetings

C.  

Simultaneous release in one pipeline

D.  

Synchronization to a common cadence