PSD Sample Questions Answers

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

True

False

To make the code more readable

To make it easy to distinguish between different software products

To communicate the identity of the developer that wrote the code

To reduce friction in a shared codebase

To ensure that orphan functions are not created

A technical requirement that must be satisfied

A bug

Great development practices

Something that completes the test coverage of a system

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

Every sprint to remain agile

Never, it will reduce the velocity

As needed, but it should not affect the productivity

It does not measure usability

It is too complicated to explain to management

It only provides insights to programmers

It does not ensure that the most important or highest risk areas of the code are being exercised by tests

It could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing code coverage

Execution is fast

Independent of others

Includes exercising the persistence layer

Makes assertions about only one logical concept

The scrum process

All of these

The increment

Coding and engineering practices

False

True

After the tests passes

When preparing legacy code for unit tests

When I can see the debt building in the code

After the tests fails

True

False

False

True

Scrum requires a specific set of development practices

Scrum is complemented by good development practices

Scrum requires all development practices

Scrum has no relationship to development practices

Managers assign individuals to teams

Get all the people together and let them self-manage into new teams

Scrum master chooses a few team leads that get to pick their team

The chief product owner divides the group in teams to make sure the teams will be cross-functional

Existing teams propose how they would like to go about organizing into new teams

A test of the user interface

A test that runs during a continuous integration build

A test of multiple units of functionality

A test of a single unit of functionality