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

When the Product Owner says it is ready.

At the end of Sprint Planning.

When the Scrum Team agrees it is precise enough.

When the Product Backlog Refinement timebox expires.

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.

True

False

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

By keeping high-value features high in the Product Backlog.

By facilitating Scrum Team decisions.

By ensuring the meetings start and end at the proper time.

By removing impediments that hinder the Scrum Team.

A term representing the eventual consequences of poor technical choices

Developers that have to pay college debt

Code that hasn’t been documented

The money an organization owes to tool and hardware vendors

The architect chosen by the developers

The architect chosen by the developers

The assigned architect

The developers

transparency

planning

inspection

respect

commitment

adaptation

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

Resolving conflicts amongst the developers

Selecting the product owner

Organizing work required to meet the sprint goal

Reporting productivity

Vague statements or untested assumptions

Assigning blame

Generic titles

Simple and repeatable reproduction steps

One bug per report

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

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress

Finding bugs

Tracking quality metrics

All developers are responsible for quality

Verifying the work of the programmers

Scrum has no tester role

The developers

Product owner

The company’s database specialist

Scrum master

The Scrum Team has all the skills to create an Increment by the end of every Sprint.

Every member of the Scrum Team is able to perform every task.

There are no conflicts within the Scrum Team.

A few of the Developers pair program and do Test-Driven Development.

A unit tests only runs on the developer’s computer

A unit test is automated

An integration test runs overnight

A unit tests isolates a specific system behavior

An integration test may be composed of unit tests

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

True

False

When all the tasks are completed by the Developers.

When the Sprint Retrospective is complete.

When all Product Backlog items meet their Definition of Done.

When the Product Owner decides enough has been delivered to meet the Sprint Goal.

Continuous Integration / Continuous Deployment / Continuous Delivery.

Blue-Green-Deployment.

Hypothesis-Driven Development.

Vertical Teams.

Blameless Post-Mortems.

All of the above.

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

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

Release planning

Daily scrum

Sprint review

Sprint retrospective

Refinement meeting

Manage the meeting

All of these

Lead the discussion

Ensure that the meeting takes place and that its timebox won't be exceeded

Make sure all three questions of the daily scrum are answered

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 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

Fix the bug

Revise the tests to hide the bug from the tests reports

Talk to the product owner

Stub out the code that causes the bug

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

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

Extracting methods

Reordering method parameters to improve readability

Changing external interfaces or APIs

Renaming things to be more logical

Extracting interfaces

False

True

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

Product goal

Sprint goal

Sprint planning outcome

Definition of 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

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

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.

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

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

Sprint Retrospective

Developers must stand up at the Daily Scrum.

Sprint Burndown Chart.

Release Planning.

All of the above.

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

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.

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development