先試後買

A. Re-architect the system so that there are no dependencies between the teams; integration is not required at this time

B. Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned

C. Have every team demonstrate their team increment to the stakeholders separately in the team branch

D. Find a vendor that specializes in integrating system increments from multiple teams

A. Accepted

B. Mitigated

C. Owned

D. Resolved

A. To identify improvement Story candidates

B. To review how value flows through the Agile Release Train

C. To identify the issues to address during the problem-solving workshop

D. To learn from PI Planning outcomes

A. During the daily stand-up

B. At the Inspect and Adapt event

C. During PI Planning

D. At the System Demo

A. Be aligned with Product Management when reviewing the Team's Backlog

B. Hold team members accountable to complete their tasks by monitoring task progress deviation

C. Enforce Agile event timeboxes and working agreements

D. Ensure team velocity and WIP are a true representation of what is happening within the team

A. Hackathons

B. Inspect and Adapt

C. Backlogrefinement

D. Pair work

E. Communities of Practice

F. Iteration planning

A. When making frequent decisions

B. When there are significant economies of scale

C. When decisions need specific local context

D. When decisions are short-term in duration