Scrum PSD Professional Scrum Developer 1 (PSD I) Exam Practice Test

False, the scrum master does that

True

True, in line with what was promised to the stakeholders

True, if the developers have enough capacity

False, the project manager does that

False

They support Continuous Integration

The eliminate the need for build engineers

They ensure your product remains bug free

They clearly define the build process

They allow frequent validation and ensure the product remains in a potentially releasable state

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

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

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.

Do all the work except for deployment

Complete the work in the within the foreseen time and costs

Create a potentially releasable increment from the product backlog items

Team manager

Project manager

Requirements engineer

Mediator for the developers and customers

Value optimizer

Visual representation of work that is still to do and time that is left

A chart showing progress towards the product goal

A chart that shows whether bugs came up

Visual representation of the product backlog items left

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

Each team’s automated build is integrated toward the end of the sprint

Developers should perform a combination of local and private builds

Each team should have its own automated build

There is one automated build for all teams

sprint retrospective

sprint goal meeting

backlog refinement

sprint planning

sprint review

daily scrum

The Sprint is extended temporarily. Lessons are taken to ensure it does not happen again.

The Sprint length is unchanged, and the Scrum Team continuously learns and adapts.

The Sprint is extended, and future Sprints use this new duration.

True

False

Definition of done

Sprint goal

Sprint planning outcome

Product goal

True

False

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.

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.

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

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

Analyze, describe, and document the requirements for the subsequent Sprints.

Define the major product features and a release plan architecture.

Make up a plan for the rest of the project.

Create at least one valuable and useful Increment.

Improving code quality

All of these

It is a nice way to work

Information sharing and learning

Efficiency

Every team must make their own DoD, a meeting should be organised so that the differences are known.

It depends on the product owner

All development teams must have a DoD that makes their combined work releasable.

Every team uses its own. The differences are discussed in a hardening sprint.

True

False

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

This way documentation is obligated and cannot be skipped

It creates a shared understanding of what done means

Management knows what the work of the developer needs to be checked for

It helps the developers know how much work to select during the sprint planning

The feature-branch is generally kept in a buildable state.

Know immediately how a change affected the product.

Reduce effort and risk when integrating changes.

Readability of code is improved.

False

True

Release documentation

Build automation

Security

Design pattern choices

Scalability

True

False

An approach to make decisions easier to change in the future and find the best possible point in time to make decisions.

Starting development of a software product requires a clear understanding of the underlying software architecture, and Emergent Architecture describes the process of creating this final architecture.

In Scrum there is no Architect-Role; therefore, architecture emerges naturally.

Enterprise Architects must be involved to create the foundation of each software product.

The software architecture emerges solely from decisions the Developers make from a technical perspective.

During the sprint planning when they can’t fit enough into the sprint

Prior to starting a new sprint

In the retrospective when it turns out they can improve quality

Prior to starting a new project

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

Exploratory.

Functional.

Unit.

Integration.

Manual regression.

Performance.

Scrum requires no documentation

Technical writers

Scrum master

Product owner

Developers

A technique for ensuring that units of co-dependent systems integrate correctly

A way to ensure product code satisfies the user requirements

A test that isolates and verifies individual units of functionality

A test that ensures a specific method integrates properly with the code calling it

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

True

False

False

True

Developers

Developers and product owner

Product owner

Scrum team

Scrum master and product owner

Scrum master

Create a plan for testing the application

Identify tools and techniques to be used in testing the product

Define acceptance criteria for features

Delay test activities until a feature has been coded

Enough to deploy the increment and update the product backlog based on the outcome of the sprint review

Enough to clean up lingering definition of done points

None, a new sprint starts immediately after the end of the previous one

At most a week for a one-month sprint

It is designed along with the vision, before the first Sprint.

In the beginning of the project, during Sprint 0.

Before writing code.

Throughout development, as understanding emerges.

A culture of continuous experimentation and learning.

To deliver value earlier and more frequently.

A tool-focused way of introducing DevOps, compared to a mindset way (second way) and organizational structure (third way).

Using automated build and release pipelines.

The first set of practices a team should apply before moving to the second way.

True

False

When the developers feel they aren't ready

When the project manager decides this.

Never, the sprint must always be finished.

When the sprint goal becomes obsolete

It is a complete user story with all the necessary components

It is well understood by the developers and product owner at the sprint planning

It has been changed from unready to ready status in the tracking tool

It has been fully described in the user requirements analysis

It can most likely be done within one sprint

Deductive

Hybrid

Empirical

Technical

Release burn-up.

Burn-down chart.

Unit tests.

Critical path analysis.

Refactoring.

Build automation.

None of the above.