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

All of these

Anytime the developers need feedback from the product owner

Whenever the product owner asks

During the sprint review

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.

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

The Product Owner.

The Scrum Team.

The Scrum Master.

The Developers.

False

True

The Developers may forecast less overall work in Sprint 8.

Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting.

There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint.

The Developers carry over incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work.

The Scrum Master adds additional Developers for Sprint 8.

The Developers put incomplete Product Backlog items back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8.

Definition of done

Sprint goal

Sprint planning outcome

Product goal

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

False

True

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

Team manager

Project manager

Requirements engineer

Mediator for the developers and customers

Value optimizer

An incremental and emergent approach to software design

A software development technique based on automated tests

A predictable way to develop working well-organized code

Creating a manual test script before writing code

Having testers involved in the development process

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

Daily Scrum

Sprint

Sprint planning

All of these

Sprint review

Sprint retrospective

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

False

True

True

False

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.

Discover decisions to be made as soon as possible but postpone making those decisions until the latest reasonable moment.

Making decisions as soon as possible to close feedback loops as soon as possible.

The last moment in a Sprint when code changes are allowed; after this, only stabilization work should be conducted.

The last moment a Developer is responsible for quality; after this, the Tester is responsible.

sprint retrospective

sprint goal meeting

backlog refinement

sprint planning

sprint review

daily scrum

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

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

Function points

Cyclometic complexity

Depth of inheritance

Keeping stakeholders at bay

Optimizing the value of the developers’ work

Managing the project and ensuring the work gets done in line with the requirements

Directing the developers

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

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

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

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress

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

True

False

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

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

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

A technical requirement that must be satisfied

A bug

Great development practices

Something that completes the test coverage of a system

The Scrum Master.

The Product Owner.

Quality Assurance Specialists.

The Developers.

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

Screenshots or pictures of the bug in action, if possible

Explains some new system functionality desired

Includes build or version number where bug was found

Expected results and observed results

Provides simple and repeatable reproduction steps

Includes code for a proposed fix

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.

You are unable to check in code without them

They help you find defects and configuration management issues

Without them you can’t tell if your code works

They are part of the Definition of Done

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

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

Release burn-up.

Burn-down chart.

Unit tests.

Critical path analysis.

Refactoring.

Build automation.

None of the above.

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.