Scrum PSD Professional Scrum Developer (PSD) Exam Practice Test

The behavior of a given object can be emulated to the system under test

They are machine-generated and eliminate the need to write code by hand

To increase tight coupling

TDD is impossible without them

Isolating a particular system component for controlled testing

True

False

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

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

Execution is fast

Independent of others

Includes exercising the persistence layer

Makes assertions about only one logical concept

It has always been documented in the past

The documentation is used to enhance and maintain the software

The scrum master demands it

The software tool being used requires it

It is required by the definition of done

It promotes good design and separation of concerns

It causes you to construct a test harness that can be automated

It improves quality and reduces bugs

D It reduces the cost of maintenance over time

It ensure there will be no bugs in the code

The need for a stable velocity

The benefit of the teams figuring it out theirselves

The need to have all developers busy with work

The ability of the scrum teams to produce integrated increments

Identifying a particular codebase as ready for distribution

Combining two or more versions of code into a single codebase

Copying a portion of a codebase to isolate it from the original codebase

Two or more developers working together to ensure proper coding and configuration management

Work together and self manage to create value

Design the full architecture before starting

Creating a plan for the entire project

Create a potentially shippable functionality in the sprint

Definition of done

Sprint goal

Sprint planning outcome

Product goal

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

Combining two or more branches of code into a single code base

Creating a copy of existing code, isolated from the original code

Releasing a specific codebase into a production environment

Tagging or labeling a particular codebase as production ready

The ratio of the number of tests to lines of code in the system being tested

The quality of unit tests being written

Code being exercised by tests

The absence of defects in code

When a feature is done

Developers

Developers and product owner

Product owner

Scrum team

Scrum master and product owner

Scrum master

It is a chance for inspecting the outcome of a sprint and determining the next steps

It is a mechanism to control the work of the developers

It is a demo of the work that was done

False

True

Immediately.

Don't fix it immediately, but change the test to not show it as a temporary fix.

Don't fix it, but stub out the code that causes it.

Depends on what the product owner wants.