최신Scrum Professional Scrum Developer - PSD무료샘플문제

A. A mock is a way to initialize the database for testing

B. A test object that mimics the behavior of a dependency in the system under test

C. Mocks, stubs, dummies, fakes and shims are all the same

D. A mock helps you create a build script

A. No, because the increment has to be approved at the Sprint Review before it can be released, and a 2- week Sprint would not be considered continuous.

B. No, because before releasing an Increment it first has to fulfill the Definition of Done.

C. No, because the Product Owner may not be available each time a PBI is done, and the Product Owner has to decide if it should be released.

D. Yes, there is nothing in Scrum that conflicts with Continuous Delivery.

E. No, because stakeholders may have already seen the new features and the Sprint Review will be meaningless.

A. It is a list of all the requirements that will have to be added to the product

B. It is mainly meant as inspiration for the sprint planning

C. It is an emergent, ordered list of what is needed to improve the product

D. It is the diary of the product owner

A. The build is executed once every night and at least once each weekend.

B. It can increase collaboration within the Developers.

C. It leads to higher transparency and rapid feedback for the team.

D. It eliminates bugs completely.

A. Two programmers writing code separately, but always review each other's pull requests

B. Two developers writing code together, providing constant peer review

C. Developer and tester work together to write and test code

D. Managers doing performance reviews by comparing one programmer's code to another's

A. Immediately raise the issue to the Scrum Master.

B. Complete the work that can be done and complete the remainder during the "hardening sprint".

C. Cancel the Sprint.

D. Stop using Scrum until the impediment is resolved.

E. Drop the Product Backlog items affected by the impediment from the Sprint Plan.

A. The need for a stable velocity

B. The benefit of the teams figuring it out theirselves

C. The need to have all developers busy with work

D. The ability of the scrum teams to produce integrated increments

A. Sprint planning

B. Sprint retrospective

C. Sprint

D. Sprint review

E. All of these

F. Daily Scrum

A. In the retrospective when it turns out they can improve quality

B. Prior to starting a new sprint

C. Prior to starting a new project

D. During the sprint planning when they can't fit enough into the sprint

A. It is baselined to follow change management processes.

B. It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan.

C. It provides just enough information to enable a Scrum Team to start the design phase of a product.

D. It is allowed to grow and change as more is learned about the product and its customers.

A. Inform the product owner, so the PO can deal with the CEO

B. Add the item to the next sprint

C. Add the item to the current sprint and work harder

D. Add the item to the current sprint and leave out something that is less important

A. Burn-down chart.

B. Critical path analysis.

C. None of the above.

D. Refactoring.

E. Release burn-up.

F. Unit tests.

G. Build automation.

A. Enough to clean up lingering definition of done points

B. At most a week for a one-month sprint

C. None, a new sprint starts immediately after the end of the previous one

D. Enough to deploy the increment and update the product backlog based on the outcome of the sprint review

A. Improving code quality

B. Efficiency

C. All of these

D. It is a nice way to work

E. Information sharing and learning