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

The developers

Everyone invited by the product owner

The scrum master

The manager of the IT department

It is optional, no one has to attend

The product owner

The degree to which the system under test has been exercised by tests.

The number of Developers that understand how the code works.

An insurance policy that covers the code for defects.

The percentage of code in version control included in a build.

Keeping stakeholders at bay

Optimizing the value of the developers’ work

Managing the project and ensuring the work gets done in line with the requirements

Directing the developers

Sprint Retrospective

Developers must stand up at the Daily Scrum.

Sprint Burndown Chart.

Release Planning.

All of the above.

Architecture is an ongoing discussion amongst the developers, focusing on implementing current Sprint Backlog Items

The developers focus only on adding functionality. The architecture will take care of itself as the developers add functionality

The developers have a set of guiding architecture principles that every developer understands and follows when writing code

Developers assign someone to the role of software architect to ensure the architecture

Architecture is dealt with in sprint 0

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

Manage the meeting

All of these

Lead the discussion

Ensure that the meeting takes place and that its timebox won't be exceeded

Make sure all three questions of the daily scrum are answered

The business analyst

The sales manager

The scrum master

The developers

The project manager

The product owner

It is a great way for Testers to contribute early in the Sprint as they can start creating all the tests from the beginning.

It increases collaboration between Developers as it requires Pair Programming.

It helps to identify gaps in understanding the desired behavior.

It might lead to better code as refactoring is part of the Test-Driven Development cycle.

It helps break down complex problems into smaller ones that are much easier to be tackled.

It makes Integration Tests obsolete and by doing so saves a lot of time.

Handle them during a risk mitigation phase before development

Scrum is for functional, frontend development only

Include them in the Product Backlog

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

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

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