SAFe-SASM 無料問題集「Scrum SAFe Advanced Scrum Master (SASM)」

（A）Limits on WIP preventvisibilityinto bottlenecks

（B）More WIP leads to slower throughput

（C）WIP should be managed by the team's capacity allocation

（D）WIP visibility increases cross-training opportunities

（A）To create the Program Board

（B）To track Iteration plans across teams

（C）To identify dependencies across teams

（D）To track planning progress across the ART

（A）Identify impediments

（B）Facilitate cross-team collaboration

（C）Review Solution Architecture

（D）Collaborate release details with Systems Team

（A）Decouple deployment from release

（B）Create all Features using behavior-driven development

（C）Couple development cadence and deployment cadence

（D）Automate all unit-tests

（A）Find a vendor that specializes in integrating system increments from multiple teams

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

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

（D）Have every team demonstrate their team increment to the stakeholders separately in the team branch

（A）Create a buffer state between the two states to regulate the situation

（B）Combine the two states to avoid the varying work flow

（C）Redesign the board toensure a smooth flow of work

（D）Match skill sets to the WIP states and hold individuals accountable in order to smooth out flow