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

True

False

As needed, taking into account a short term reduction in productivity

Every sprint to remain agile

Never, it will reduce the velocity

As needed, but it should not affect the productivity

Scrum team

The product owner

Developers

The scrum master lets them know whether they need to be preset

False

True

All of these

Anytime the developers need feedback from the product owner

Whenever the product owner asks

During the sprint review

It is an emergent, ordered list of what is needed to improve the product

It is the diary of the product owner

It is mainly meant as inspiration for the sprint planning

It is a list of all the requirements that will have to be added to the product

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.

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.

transparency

planning

inspection

respect

commitment

adaptation

Product goal

Sprint goal

Sprint planning outcome

Definition of done

The Scrum Master.

The Product Owner.

Quality Assurance Specialists.

The Developers.

In production during peak hours

Often during the development

In production

Just before deployment to production

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 with the QA departments on the increment of the current sprint

Update the project plan with stakeholders

Refine the backlog

There are no such activities. The next sprint starts immediately after the current sprint

Just before the first check-in

Just before the product is released

When the product owner asks for a build

Just before the end of the sprint

As soon as there is code in the version control system

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

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

Because testers are terrible coders

Because the tests are checked in before the code exists

Because the product code to satisfy the test doesn’t exist yet

Because the test needs to be refactored

Less than 50% of the application is working correctly

There are no bugs in the application

At least 50% of the application is working correctly

You did not break any of the unit tests that already existed

True

False

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

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

False

True

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

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

Release burn-up.

Burn-down chart.

Unit tests.

Critical path analysis.

Refactoring.

Build automation.

None of the above.

Scrum requires no documentation

Technical writers

Scrum master

Product owner

Developers

Changes to the project plan were not adequately documented and shared

The product owner has not been keeping the stakeholders aware of the progress of the project

The project management office has not been engaged adequately

The scrum master has not ensured that the project is transparent

The stakeholders were not allowed to enter the development area

The stakeholders haven’t been using sprint reviews to inspect and evaluate progress

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.

Code with low cyclomatic complexity

Code with minimal duplication

Code that has not been peer reviewed (yet)

Code that has been peer reviewed

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

Doing all work needed to meet the Definition of Done.

Updating Sprint tasks properly in the electronic tracking tool.

Keeping track of and estimating all undone work to be completed in a “hardening" Sprint.

Reporting Sprint progress to the stakeholders daily.

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

False

True

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

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

From the beginning and throughout all Sprints.

When the implementation of each feature is complete.

After Sprint Review.

When the product is feature complete.

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.

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

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

True

False

False, the scrum master does that

True

True, in line with what was promised to the stakeholders

True, if the developers have enough capacity

False, the project manager does that

False

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

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