A. To facilitate collaboration with other team members
B. To identify the customer
C. To gain deeper insight to the members of an Agile Team
D. To help develop a deeper understanding of the customer
A. To show dependencies between teams relating to the Feature development
B. To satisfy System Demo expectation by demonstrating incremental delivery
C. To show sizing of the Epics in relation to each other
D. To show Feature priority in association with business value
A. Program Backlog
B. Weighted shortest job first
C. Team Backlogs
D. Release on Demand
A. Lean systems Engineering
B. DevOps and Release on Demand
C. Lean Portfolio Management
D. Team and Technical Agility
A. Functional teams
B. Solutions
C. Business units
D. Development Value Streams
A. PI System Demo
B. Retrospective and problem-solving workshop
C. Agreement on the problems to solve
D. Quantitative measurement
A. Train teams and launch ARTs
B. Enhance the Portfolio
C. Create the implementation plan
D. Prepare for ART launch
A. It serves as a way to estimate large ranges
B. It can be used to predict unit test coverage
C. It results in greater precision
D. It reflects the uncertainty in estimating larger items
A. Compliance
B. Exploration
C. Architecture
D. Infrastructure
A. The PO does not need to attend
B. Items are assigned to the team members
C. It occurs on the last day of the Iteration
D. It is required for every Iteration to enable fast learning cycles
A. How the team is responding to the stakeholders
B. How the team did on the Iteration
C. How the team is demonstrating transparency of decision-making
D. How the team is increasing empowerment
E. How the team is doing on the Program Increment
A. During the qualitative part of the team retrospective
B. During the time and materials retrospective
C. During the quantitative part of the team retrospective
D. During the Features agreement retrospective
B. Key stakeholders
C. Customers
D. PI Planning
