PSD 無料問題集「Scrum Professional Scrum Developer」

（A）Releasing a specific codebase into a production environment

（B）Tagging or labeling a particular codebase as production ready

（C）Creating a copy of existing code, isolated from the original code

（D）Combining two or more branches of code into a single code base

（A）Extracting interfaces

（B）Changing external interfaces or APIs

（C）Renaming things to be more logical

（D）Extracting methods

（E）Reordering method parameters to improve readability

（A）Know immediately how a change affected the product.

（B）The feature-branch is generally kept in a buildable state.

（C）Reduce effort and risk when integrating changes.

（D）Readability of code is improved.

（A）As much as needed without endangering the Sprint goal

（B）25% of the sprint capacity

（C）10% of the senior developers

（A）Work or value

（B）Visual representation of the progress

（C）Work that needs to be done

（D）Flow and feedback

（A）Updating Sprint tasks properly in the electronic tracking tool.

（B）Keeping track of and estimating all undone work to be completed in a "hardening" Sprint.

（C）Doing all work needed to meet the Definition of Done.

（D）Reporting Sprint progress to the stakeholders daily.

（A）Mocks, stubs, dummies, fakes and shims are all the same

（B）A mock is a way to initialize the database for testing

（C）A test object that mimics the behavior of a dependency in the system under test

（D）A mock helps you create a build script

（A）Every sprint to remain agile

（B）Never, it will reduce the velocity

（C）As needed, taking into account a short term reduction in productivity

（D）As needed, but it should not affect the productivity

（A）Specific expectations can be used as acceptance criteria to specific product backlog items

（B）Before the release, they should be tested and validated in a hardening sprint

（C）Include them in the Product Backlog

（D）Handle them during a risk mitigation phase before development

（E）Important, recurring non-functional requirements can be added to the definition of done

（F）Scrum is for functional, frontend development only

（A）By being a lightweight framework.

（B）By the Scrum Team deciding what work to do in a Sprint.

（C）By having the Scrum Master protect the Scrum Team.

（D）By removing titles for Scrum Team members.