Free Scrum PSD Practice Exam with Questions & Answers

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

Unit tests per class

Cycle time per product backlog item

Number of check-ins per day

Depth of inheritance

Cyclomatic complexity

Class coupling

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

Measuring branching structures and nesting levels in code

Assessing if code is written in as few lines as possible

Determining the number of unit tests required to ensure correctness

Demonstrating code is well structured and cleanly implemented

Release documentation

Build automation

Security

Design pattern choices

Scalability

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

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

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.

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

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