Free Scrum PSD Practice Exam with Questions & Answers | Set: 5

It defines a state when the entire Increment is releasable.

It might be a subject of discussion during the Sprint Retrospective.

It is synonymous with acceptance criteria.

It is the sole responsibility of the Developers to define it.

It can only be extended; nothing can be removed.

Scrum requires no documentation

Technical writers

Scrum master

Product owner

Developers

Code with low cyclomatic complexity

Code with minimal duplication

Code that has not been peer reviewed (yet)

Code that has been peer reviewed

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

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

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

True

False

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.