PSD Professional Scrum Developer 1 (PSD I) Questions and Answers

A technical requirement that must be satisfied

A bug

Great development practices

Something that completes the test coverage of a system

Scrum is a framework for developing and sustaining complex products.

Each component of scrum serves a specific purpose and is essential to Scrum's success

Scrum is based on empirical process control

Scrum is like traditional project management, but then with project managers replaced by self-management.

Scrum is a methodology based on empirical process control.

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

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.

Team manager

Project manager

Requirements engineer

Mediator for the developers and customers

Value optimizer

The architect chosen by the developers

The architect chosen by the developers

The assigned architect

The developers

It defines a state when the entire Increment is releasable.

It might be a subject of discussion during the Sprint Retrospective.

It is synonymous with acceptance criteria.

It is the sole responsibility of the Developers to define it.

It can only be extended; nothing can be removed.

It is allowed to grow and change as more is learned about the product and its customers.

It provides just enough information to enable a Scrum Team to start the design phase of a product.

It is baselined to follow change management processes.

It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan.

Why is this sprint valuable?

When is this sprint going to be done?

How to improve the scrum process in this sprint?

How will the selected work get done?

What can be done in this sprint?

Who is going to do what?

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

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.

transparency

planning

inspection

respect

commitment

adaptation

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.

Set aside the Sprint Goal until the bug is fixed.

Revise the tests so that the bug no longer appears on the bug report.

Stub out the code that caused the bug so it no longer occurs.

Talk to the Product Owner about what steps to take.

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

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

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

True

False

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

True

False

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

Unit tests per class

Cycle time per product backlog item

Number of check-ins per day

Depth of inheritance

Cyclomatic complexity

Class coupling

Developers

Developers and product owner

Product owner

Scrum team

Scrum master and product owner

Scrum master

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

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

Add the item to the next sprint

Add the item to the current sprint and work harder

Add the item to the current sprint and leave out something that is less important

Inform the product owner, so the PO can deal with the CEO

Analysis performed on software at runtime

A tool that inspects the correctness of static keyword usage

Work performed by the business analyst

Analysis performed on code

By being a lightweight framework.

By the Scrum Team deciding what work to do in a Sprint.

By removing titles for Scrum Team members.

By having the Scrum Master protect the Scrum Team.

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

Product goal

Sprint goal

Sprint planning outcome

Definition of done

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

Code review is done

Acceptance tests pass

Regression tests pass

The product is released at the end of every sprint

Code coverage 90%

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

Managers doing performance reviews by comparing one programmer’s code to another’s

Two developers writing code together, providing constant peer review

Two programmers writing code separately, but always review each other’s pull requests

Developer and tester work together to write and test code

Function points

Cyclometic complexity

Depth of inheritance

Vague statements or untested assumptions

Assigning blame

Generic titles

Simple and repeatable reproduction steps

One bug per report

The business analyst

The sales manager

The scrum master

The developers

The project manager

The product owner

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

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.

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.

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

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

Scrum requires no documentation

Technical writers

Scrum master

Product owner

Developers

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.