[2022] PSD Actual Exam Dumps, PSD Practice Test [Q61-Q84]

PSD Scrum

admin • November 19, 2022

[2022] PSD Actual Exam Dumps, PSD Practice Test [Q61-Q84]

Rate this post

[2022] PSD Actual Exam Dumps, PSD Practice Test

2Pass4sure PSD dumps & Scrum Certification sure practice dumps

Q61. What is static analysis?

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

Static analys is performed on code (and not a running program or build).

Q62. Who must attend the daily scrum? Choose all that apply.

The developers

Everyone invited by the product owner

The scrum master

The manager of the IT department

It is optional, no one has to attend

The product owner

The scrum guide says: “The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. “

Q63. When a continuous integration build fails, who should fix it?

The person who is responsible for configuration management within the team

The person who broke the build

The tester responsible for validating builds

The next person who needs the build to complete successfully

The build should be fixed asap, the first person to notice is the person who broke it. This person usually best understands why and is therefore the best person to fix it.

Q64. Who writes tests in a scrum team?

Most junior developer

Product owner

QA specialists

Scrum master

The tester

Developers

Tests are part of the development, and the development is done by the developers. There are no specific roles in scrum, even though members of the scrum team can have their own expertise.

Q65. Upon what type of process control is scrum based?

Deductive

Hybrid

Empirical

Technical

If you are not sure, please review the Scrum theory section in the scrum guide

Q66. Which statement best describes the sprint review?

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 scrum guide says: “The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. “

Q67. When do the developers participate in the product backlog refinement?

Never, it is the sole responsibility of the Product owner to refine the backlog

Only during the sprint planning

Anytime during the sprint

Only during the refinement meetings planned by the PO

There is no set time for product backlog refinement.

Q68. What are three of the best ways to address non-functional requirements?

Handle them during a risk mitigation phase before development

Scrum is for functional, frontend development only

Include them in the Product Backlog

Before the release, they should be tested and validated in a hardening sprint

Specific expectations can be used as acceptance criteria to specific product backlog items

Important, recurring non-functional requirements can be added to the definition of done

There is no hardening sprint, there are only regular sprints. If it’s an ever recurring non-functional requirement, it can be added to the definition of done. If it’s not it can be added (as a criteria) in the product backlog (item).

Q69. The increment must be released at the end of the sprint

True

False

It should be a working increment, but it’s not mandatory to release it.

Q70. The scrum team should change in members:

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

Changing the team members is sometimes necessary, this will have an effect on productivity. So it should only be used when really necessary.

Q71. If multiple teams are working on the same product, each team should have its own product owner

False

True

One product owner per product backlog, one product backlog per product

Q72. What is the commitment for the sprint backlog?

Definition of done

Sprint goal

Sprint planning outcome

Product goal

If you are not sure, please review the section scrum artifacts in the scrum guide.

Q73. The practice of decomposing a requirement into failing tests is called:

Behavior driven development

Scrum testing

Regression testing

Acceptance test driven development

In ATDD you start with writing tests to represent the requirement. Since you start with this, there is no production code to satisfy the test which is why the tests will fail.

Q74. Which best describes the practice of expressing requirements as acceptance tests?

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

This is pretty much the definition of ATDD.

Q75. What is the practice of branching code in a version control system?

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

Branching means that you create a new version from the code that exists indepently from the original code. It is not isolated forever, it can be merged back later.

Q76. Which three of the following are code quality metrics?

Unit tests per class

Cycle time per product backlog item

Number of check-ins per day

Depth of inheritance

Cyclomatic complexity

Class coupling

Number of checkins per day says something about whether the developers are committing often enough. Depth of inheritance says some about complexiity, just like class coupling and cyclomatic complexity. Unit tests per class don’t say anything about quality, though no unit tests might indicate a maintenance problem. Cycle time per product backlog item says something about the scrum process.

Q77. When more teams are working on the same product. How should they go about their definition of done?

Every team must make their own DoD, a meeting should be organised so that the differences are known.

It depends on the product owner

All development teams must have a DoD that makes their combined work releasable.

Every team uses its own. The differences are discussed in a hardening sprint.

The product must be releasable and done must mean the same for all additions to the product. So they must have a DoD that can combined. There is no hardening sprint.

Q78. Which are topics of the sprint planning? Choose all that apply.

Why is this sprint valuable?

When is this sprint going to be done?

How to improve the scrum process in this sprint?

How will the selected work get done?

What can be done in this sprint?

Who is going to do what?

These are the three topics mentioned in the scrum guide. Who is going to do what is not determined upfront, when the sprint will end is fixed and doesn’t need to be discussed, what can be done to improve the process is for the sprint retrospective meeting.

Q79. What is the role of modeling in scrum teams?

Models are not used by agile teams

Models are maintained along with the software as it emerges

Models are assembly instructions for the developers

Modeling may be useful to increase shared understanding

Models are in no way mandatory, however their value as increasing shared language is acknowledged.

Q80. What are some disadvantages of code coverage as a measure for how well a system or product is tested? (three answers)

It does not measure usability

It is too complicated to explain to management

It only provides insights to programmers

It does not ensure that the most important or highest risk areas of the code are being exercised by tests

It could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing code coverage

Not being able to explain to management should never be the reason to not do it. It doesn’t only provide some data to programmers, the problem is that code coverage alone is not meaning a lot.

Q81. Scrum demands code review

True

False

There are no concrete development guidelines demanded by scrum, even though code review is an excellent idea. Scrum is also not only about developing software.

Q82. What do scrum artifacts represent?

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress

The scrum artifacts are: product backlog, sprint backlog and the increment. They represent work or value.

Q83. The purpose of a sprint is to produce a done increment of product

False

True

The sprint is the heartbeat of scrum, during the sprint the increment is created. The increment must be usable and all the work that’s part of the increment should adhere to the definition of done.

Q84. What event is timeboxed?

Sprint retrospective

Sprint

Daily Scrum

All of these

Sprint planning

Sprint review

Loading …