Pass the Scrum Professional Scrum Developer PSD Questions and answers with ValidTests

Inform the product owner and the stakeholders during the sprint review

As soon as they realize they should work with the product owner to remove some work while not endangering the sprint goal

Outsource the work to another team

Use a definition of done with lower standards to be able to finish all the work they committed to

The Architect chosen by the Scrum Team.

The software architect assigned to the Scrum Team.

The Developers with input from the Scrum Team and others.

The Chief Architect.

The person who is responsible for configuration management within the team

The person who broke the build

The tester responsible for validating builds

The next person who needs the build to complete successfully

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

Discover decisions to be made as soon as possible but postpone making those decisions until the latest reasonable moment.

Making decisions as soon as possible to close feedback loops as soon as possible.

The last moment in a Sprint when code changes are allowed; after this, only stabilization work should be conducted.

The last moment a Developer is responsible for quality; after this, the Tester is responsible.

Because testers are terrible coders

Because the tests are checked in before the code exists

Because the product code to satisfy the test doesn’t exist yet

Because the test needs to be refactored

transparency

planning

inspection

respect

commitment

adaptation

Cancel the Sprint.

Immediately raise the issue to the Scrum Master.

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

Stop using Scrum until the impediment is resolved.

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

Additions features in a usable state that complement those delivered in previous iterations

UML diagrams that describe how to deliver functionality in future iterations

A new user interface design for functionality delivered in previous iterations

An automated test suite to verify functionality delivered in previous iterations

A decomposition of all product backlog items into tasks for future sprint backlog lists

Continuous Integration / Continuous Deployment / Continuous Delivery.

Blue-Green-Deployment.

Hypothesis-Driven Development.

Vertical Teams.

Blameless Post-Mortems.

All of the above.