Practice Free PSD Professional Scrum Developer 1 (PSD I) Exam Questions Answers With Explanation

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.

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

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

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.

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

A software development practice used by integration teams to create best practice branching and merging strategies

A software development practice that continuously integrates feedback from users in the software design

A software development practice where developers all work on the same computer to assure a common codebase

A software development practice where developers integrate and verify their work frequently, often multiple times a day, to detect integration errors as quickly as possible

However much time the developers ask the PO to be present

40%, or more depending on stakeholders

100%

Enough to be aware of the increment’s value at the sprint review

Every member can do every task

They work with TDD

They never argue

They do pair programming

Developers have the combined skills to create a usable increment

Improves quality in the requirement itself.

Promotes the use of the DRY principle.

Tracking of completeness.

Using a code generation tool, the solution can be generated from the requirements model.

Clear acceptance criteria for each feature.

False

True

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

Most junior developer

Product owner

QA specialists

Scrum master

The tester

Developers

Models are not used by agile teams

Models are maintained along with the software as it emerges

Models are assembly instructions for the developers

Modeling may be useful to increase shared understanding

Never, it is the sole responsibility of the Product owner to refine the backlog

Only during the sprint planning

Anytime during the sprint

Only during the refinement meetings planned by the PO

The product owner speaks on their behalf

The developers self-manage and they are the only management required at the daily scrum

The scrum master speaks on their behalf

The scrum master lets them know whether they need to be preset

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

Vague statements or untested assumptions

Assigning blame

Generic titles

Simple and repeatable reproduction steps

One bug per report

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

The scrum master ends the meeting when it is done

This is for the developers to decide

At most 15 minutes

At least 15 minutes

Around 15 minutes, but more if necessary

Daily Scrum

Sprint

Sprint planning

All of these

Sprint review

Sprint retrospective

Developers

Developers and product owner

Product owner

Scrum team

Scrum master and product owner

Scrum master

A mock helps you create a build script

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

A mock is a way to initialize the database for testing

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

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

True

False

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

It is the diary of the product owner

It is mainly meant as inspiration for the sprint planning

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

Definition of done

Sprint goal

Sprint planning outcome

Product goal

Work with the QA departments on the increment of the current sprint

Update the project plan with stakeholders

Refine the backlog

There are no such activities. The next sprint starts immediately after the current sprint

False

True

The continuous restructuring of software to retain flexibility

Having the tester in the development team write the test plans before coding

Creating tests before satisfying them

Testing existing code before adding more code to it

Allow the developers to self-manage and decide what to do their selves.

Raise it as an impediment and make sure that management solves it.

Create a schedule and alternate who is responsible for the daily scrum logistics

Decide the best solution and arrange a meeting to inform the developers.

True

False

An incremental and emergent approach to software design

A software development technique based on automated tests

A predictable way to develop working well-organized code

Creating a manual test script before writing code

Having testers involved in the development process

Ready to be released to end users.

Whatever the Product Owner defines as quality.

No work is left to meet the Definition of Done.

Ready for integration.

All work the Developers are willing to do.

False

True

Product goal

Sprint goal

Sprint planning outcome

Definition of done

Code with low cyclomatic complexity

Code with minimal duplication

Code that has not been peer reviewed (yet)

Code that has been peer reviewed

They may update estimates for Product Backlog items.

They do not. The Scrum Master and the Product Owner are responsible for Product Backlog refinement.

They give input on technical dependencies.

They do not. The Developers are only responsible for prioritizing technical work.

They ask QUESTION NO:s to clarify the intent of Product Backlog items.

Until everyone is done.

Max two hours for a one month sprint

Max two hours

Max four hours

Max four hours for a one-month sprint

Build.

Security.

Design pattern selection.

Scalability.

False

True

Release documentation

Build automation

Security

Design pattern choices

Scalability

Code review is done

Acceptance tests pass

Regression tests pass

The product is released at the end of every sprint

Code coverage 90%

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

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

Meet with the business analyst to ensure that the test is correct.

Write the minimum amount of product code to satisfy the test.

Run it again to make sure it really fails.

Implement the required functionality.

Refactor the test so the code passes.

Sprint Retrospective

Developers must stand up at the Daily Scrum.

Sprint Burndown Chart.

Release Planning.

All of the above.

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.