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

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

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

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

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

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.

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

Product goal

Sprint goal

Sprint planning outcome

Definition of done

True

False

Build.

Security.

Design pattern selection.

Scalability.

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.

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

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

The Scrum Master.

The Product Owner.

Quality Assurance Specialists.

The Developers.

The need for a stable velocity

The benefit of the teams figuring it out theirselves

The need to have all developers busy with work

The ability of the scrum teams to produce integrated increments

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.

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.

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.

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.

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

True

False

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

The developers

Everyone invited by the product owner

The scrum master

The manager of the IT department

It is optional, no one has to attend

The product owner

Managers assign individuals to teams

Get all the people together and let them self-manage into new teams

Scrum master chooses a few team leads that get to pick their team

The chief product owner divides the group in teams to make sure the teams will be cross-functional

Existing teams propose how they would like to go about organizing into new teams

True

False

The developers emerge architecture as the system is created

The architect works in the early part of each sprint to define the architecture of that sprint

Upfront designs are presented to the developers prior to the first sprint

The architecture cares for itself as code is written and deployed

An architect on the team undertakes all architecture tasks

False

True

It eliminates bugs completely.

It leads to higher transparency and rapid feedback for the team.

The build is executed once every night and at least once each weekend.

It can increase collaboration within the Developers.

The Product Owner.

The Scrum Team.

The Scrum Master.

The Developers.

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.

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.

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress

Increase quality

Complain only in this session to avoid complaining in the rest of the sprint

Have more fun during the sprint

Increase effectiveness

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.

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.

25% of the sprint capacity

As much as needed without endangering the Sprint goal

10% of the senior developers

True

False

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

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

True

False

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

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

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

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

All of these

Anytime the developers need feedback from the product owner

Whenever the product owner asks

During the sprint review

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.