PSD Sample Questions Answers

Product goal

Sprint goal

Sprint planning outcome

Definition of done

False

True

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

True

False

False

True

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

Developers

Developers and product owner

Product owner

Scrum team

Scrum master and product owner

Scrum master

The scrum process

All of these

The increment

Coding and engineering practices

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.

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

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

Code with low cyclomatic complexity

Code with minimal duplication

Code that has not been peer reviewed (yet)

Code that has been peer reviewed

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

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

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.

Handle them during a risk mitigation phase before development

Scrum is for functional, frontend development only

Include them in the Product Backlog

Before the release, they should be tested and validated in a hardening sprint

Specific expectations can be used as acceptance criteria to specific product backlog items

Important, recurring non-functional requirements can be added to the definition of done

Release planning

Daily scrum

Sprint review

Sprint retrospective

Refinement meeting

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

Yes, it will show code coverage which is an excellent metric of quality and progress

No, it takes too much time

No, the outcomes might disturb the developers’ focus

Yes, the tests may identify whether there are bugs that the developers should fix before proceeding

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

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

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.

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

Additions features in a usable state that complement those delivered in previous iterations

UML diagrams that describe how to deliver functionality in future iterations

A new user interface design for functionality delivered in previous iterations

An automated test suite to verify functionality delivered in previous iterations

A decomposition of all product backlog items into tasks for future sprint backlog lists

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

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

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

The Scrum Master.

The Product Owner.

Quality Assurance Specialists.

The Developers.

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

Definition of done

Sprint goal

Sprint planning outcome

Product goal

A technical requirement that must be satisfied

A bug

Great development practices

Something that completes the test coverage of a system

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.

Meet with the team to see why it fails

Change the test in a way that is passes

Run it again to verify it fails.

Write the code to satisfy the test

25% of the sprint capacity

As much as needed without endangering the Sprint goal

10% of the senior developers

Function points

Cyclometic complexity

Depth of inheritance

False

True

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

All of these

Anytime the developers need feedback from the product owner

Whenever the product owner asks

During the sprint review

Delay test activities until a feature has been coded.

Define acceptance criteria for features.

Identify tools and techniques to be used in testing the product.

Create a plan for testing the application.

Code review is done

Acceptance tests pass

Regression tests pass

The product is released at the end of every sprint

Code coverage 90%

Measuring branching structures and nesting levels in code

Assessing if code is written in as few lines as possible

Determining the number of unit tests required to ensure correctness

Demonstrating code is well structured and cleanly implemented

sprint retrospective

sprint goal meeting

backlog refinement

sprint planning

sprint review

daily scrum

A fundamental architectural problem found in an existing application

The result of an exhaustive architectural planning effort

A small development activity to learn about technical elements of a proposed solution

A decision made by a systems architect to settle disagreement amongst the developers

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress