A.  

Scrum requires no documentation

B.  

Technical writers

C.  

Scrum master

D.  

Product owner

E.  

Developers

A.  

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

B.  

Every sprint to remain agile

C.  

Never, it will reduce the velocity

D.  

As needed, but it should not affect the productivity

A.  

The need for a stable velocity

B.  

The benefit of the teams figuring it out theirselves

C.  

The need to have all developers busy with work

D.  

The ability of the scrum teams to produce integrated increments

A.  

Vague statements or untested assumptions

B.  

Assigning blame

C.  

Generic titles

D.  

Simple and repeatable reproduction steps

E.  

One bug per report

A.  

They may update estimates for Product Backlog items.

B.  

They do not. The Scrum Master and the Product Owner are responsible for Product Backlog refinement.

C.  

They give input on technical dependencies.

D.  

They do not. The Developers are only responsible for prioritizing technical work.

E.  

They ask QUESTION NO:s to clarify the intent of Product Backlog items.

A.  

Do all the work except for deployment

B.  

Complete the work in the within the foreseen time and costs

C.  

Create a potentially releasable increment from the product backlog items

A.  

Less than 50% of the application is working correctly

B.  

There are no bugs in the application

C.  

At least 50% of the application is working correctly

D.  

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

A.  

typically 10 or fewer people

B.  

this differs every sprint

C.  

at least 8 people

D.  

3 to 11

A.  

Extracting methods

B.  

Reordering method parameters to improve readability

C.  

Changing external interfaces or APIs

D.  

Renaming things to be more logical

E.  

Extracting interfaces

A.  

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

B.  

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

C.  

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

D.  

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

A.  

False

B.  

True

A.  

When the Product Owner says it is ready.

B.  

At the end of Sprint Planning.

C.  

When the Scrum Team agrees it is precise enough.

D.  

When the Product Backlog Refinement timebox expires.

A.  

It promotes good design and separation of concerns

B.  

It causes you to construct a test harness that can be automated

C.  

It improves quality and reduces bugs

D It reduces the cost of maintenance over time

D.  

It ensure there will be no bugs in the code

A.  

Improving code quality

B.  

All of these

C.  

It is a nice way to work

D.  

Information sharing and learning

E.  

Efficiency

A.  

Release planning

B.  

Daily scrum

C.  

Sprint review

D.  

Sprint retrospective

E.  

Refinement meeting

A.  

Work that needs to be done

B.  

Flow and feedback

C.  

Work or value

D.  

Visual representation of the progress

A.  

Improves quality in the requirement itself.

B.  

Promotes the use of the DRY principle.

C.  

Tracking of completeness.

D.  

Using a code generation tool, the solution can be generated from the requirements model.

E.  

Clear acceptance criteria for each feature.

A.  

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.

B.  

No, because stakeholders may have already seen the new features and the Sprint Review will be meaningless.

C.  

No, because before releasing an Increment it first has to fulfill the Definition of Done.

D.  

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.

E.  

Yes, there is nothing in Scrum that conflicts with Continuous Delivery.

A.  

The developers

B.  

Product owner

C.  

The company’s database specialist

D.  

Scrum master

A.  

Most junior developer

B.  

Product owner

C.  

QA specialists

D.  

Scrum master

E.  

The tester

F.  

Developers

A.  

The Developers may forecast less overall work in Sprint 8.

B.  

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

C.  

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

D.  

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.

E.  

The Scrum Master adds additional Developers for Sprint 8.

F.  

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.

A.  

Meet with the business analyst to ensure that the test is correct.

B.  

Write the minimum amount of product code to satisfy the test.

C.  

Run it again to make sure it really fails.

D.  

Implement the required functionality.

E.  

Refactor the test so the code passes.

A.  

After the tests passes

B.  

When preparing legacy code for unit tests

C.  

When I can see the debt building in the code

D.  

After the tests fails

A.  

Behavior driven development

B.  

Scrum testing

C.  

Regression testing

D.  

Acceptance test driven development

A.  

Keeping stakeholders at bay

B.  

Optimizing the value of the developers’ work

C.  

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

D.  

Directing the developers

A.  

Release burn-up.

B.  

Burn-down chart.

C.  

Unit tests.

D.  

Critical path analysis.

E.  

Refactoring.

F.  

Build automation.

G.  

None of the above.

A.  

Fix the bug

B.  

Revise the tests to hide the bug from the tests reports

C.  

Talk to the product owner

D.  

Stub out the code that causes the bug

A.  

True

B.  

False

A.  

True

B.  

False

A.  

Each team’s automated build is integrated toward the end of the sprint

B.  

Developers should perform a combination of local and private builds

C.  

Each team should have its own automated build

D.  

There is one automated build for all teams

A.  

The ratio of the number of tests to lines of code in the system being tested

B.  

The quality of unit tests being written

C.  

Code being exercised by tests

D.  

The absence of defects in code

E.  

When a feature is done

A.  

Code with low cyclomatic complexity

B.  

Code with minimal duplication

C.  

Code that has not been peer reviewed (yet)

D.  

Code that has been peer reviewed

A.  

Screenshots or pictures of the bug in action, if possible

B.  

Explains some new system functionality desired

C.  

Includes build or version number where bug was found

D.  

Expected results and observed results

E.  

Provides simple and repeatable reproduction steps

F.  

Includes code for a proposed fix

A.  

Definition of done

B.  

Sprint goal

C.  

Sprint planning outcome

D.  

Product goal

A.  

Regression testing

B.  

Acceptance test driven development

C.  

Objective Driven Development

D.  

Quality Oriented Requirements Development

A.  

It is allowed to grow and change as more is learned about the product and its customers.

B.  

It provides just enough information to enable a Scrum Team to start the design phase of a product.

C.  

It is baselined to follow change management processes.

D.  

It contains all foreseeable tasks and requirements from which the Scrum Team can develop and maintain a complete project plan.

A.  

True

B.  

False

A.  

The developers emerge architecture as the system is created

B.  

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

C.  

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

D.  

The architecture cares for itself as code is written and deployed

E.  

An architect on the team undertakes all architecture tasks

A.  

Doing all work needed to meet the Definition of Done.

B.  

Updating Sprint tasks properly in the electronic tracking tool.

C.  

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

D.  

Reporting Sprint progress to the stakeholders daily.

A.  

The Product Owner.

B.  

The Scrum Team.

C.  

The Scrum Master.

D.  

The Developers.

A.  

However much time the developers ask the PO to be present

B.  

40%, or more depending on stakeholders

C.  

100%

D.  

Enough to be aware of the increment’s value at the sprint review

A.  

You are unable to check in code without them

B.  

They help you find defects and configuration management issues

C.  

Without them you can’t tell if your code works

D.  

They are part of the Definition of Done

A.  

Continuous Integration / Continuous Deployment / Continuous Delivery.

B.  

Blue-Green-Deployment.

C.  

Hypothesis-Driven Development.

D.  

Vertical Teams.

E.  

Blameless Post-Mortems.

F.  

All of the above.

A.  

A unit tests only runs on the developer’s computer

B.  

A unit test is automated

C.  

An integration test runs overnight

D.  

A unit tests isolates a specific system behavior

E.  

An integration test may be composed of unit tests

A.  

A test of the user interface

B.  

A test that runs during a continuous integration build

C.  

A test of multiple units of functionality

D.  

A test of a single unit of functionality

A.  

Ready to be released to end users.

B.  

Whatever the Product Owner defines as quality.

C.  

No work is left to meet the Definition of Done.

D.  

Ready for integration.

E.  

All work the Developers are willing to do.

A.  

Scrum requires a specific set of development practices

B.  

Scrum is complemented by good development practices

C.  

Scrum requires all development practices

D.  

Scrum has no relationship to development practices

A.  

A mock helps you create a build script

B.  

Mocks, stubs, dummies, fakes and shims are all the same

C.  

A mock is a way to initialize the database for testing

D.  

A test object that mimics the behavior of a dependency in the system under test