Free and Premium Scrum PSD Dumps Questions Answers

True

False

The business analyst

The sales manager

The scrum master

The developers

The project manager

The product owner

The sprint backlog

The product goal

The Sprint goal

Sprint review minutes

Most junior developer

Product owner

QA specialists

Scrum master

The tester

Developers

Code with low cyclomatic complexity

Code with minimal duplication

Code that has not been peer reviewed (yet)

Code that has been peer reviewed

Keeping stakeholders at bay

Optimizing the value of the developers’ work

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

Directing the developers

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

Work that needs to be done

Flow and feedback

Work or value

Visual representation of the progress

By being a lightweight framework.

By the Scrum Team deciding what work to do in a Sprint.

By removing titles for Scrum Team members.

By having the Scrum Master protect the Scrum Team.

Execution is fast

Independent of others

Includes exercising the persistence layer

Makes assertions about only one logical concept

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

The degree to which the system under test has been exercised by tests.

The number of Developers that understand how the code works.

An insurance policy that covers the code for defects.

The percentage of code in version control included in a build.

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

Ready to be released to end users.

Whatever the Product Owner defines as quality.

No work is left to meet the Definition of Done.

Ready for integration.

All work the Developers are willing to do.

Release planning

Daily scrum

Sprint review

Sprint retrospective

Refinement meeting

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

Sprint Retrospective

Developers must stand up at the Daily Scrum.

Sprint Burndown Chart.

Release Planning.

All of the above.

Resolving conflicts amongst the developers

Selecting the product owner

Organizing work required to meet the sprint goal

Reporting productivity

False

True

An approach to make decisions easier to change in the future and find the best possible point in time to make decisions.

Starting development of a software product requires a clear understanding of the underlying software architecture, and Emergent Architecture describes the process of creating this final architecture.

In Scrum there is no Architect-Role; therefore, architecture emerges naturally.

Enterprise Architects must be involved to create the foundation of each software product.

The software architecture emerges solely from decisions the Developers make from a technical perspective.

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

True

False

True

False

Increase quality

Complain only in this session to avoid complaining in the rest of the sprint

Have more fun during the sprint

Increase effectiveness

True

False

The scrum master ends the meeting when it is done

This is for the developers to decide

At most 15 minutes

At least 15 minutes

Around 15 minutes, but more if necessary

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.

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 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

Work together and self manage to create value

Design the full architecture before starting

Creating a plan for the entire project

Create a potentially shippable functionality in the sprint

All of these

Anytime the developers need feedback from the product owner

Whenever the product owner asks

During the sprint review

Release burn-up.

Burn-down chart.

Unit tests.

Critical path analysis.

Refactoring.

Build automation.

None of the above.

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.

Architecture is an ongoing discussion amongst the developers, focusing on implementing current Sprint Backlog Items

The developers focus only on adding functionality. The architecture will take care of itself as the developers add functionality

The developers have a set of guiding architecture principles that every developer understands and follows when writing code

Developers assign someone to the role of software architect to ensure the architecture

Architecture is dealt with in sprint 0

A technique for ensuring that units of co-dependent systems integrate correctly

A way to ensure product code satisfies the user requirements

A test that isolates and verifies individual units of functionality

A test that ensures a specific method integrates properly with the code calling it

True

False

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

Screenshots or pictures of the bug in action, if possible

Explains some new system functionality desired

Includes build or version number where bug was found

Expected results and observed results

Provides simple and repeatable reproduction steps

Includes code for a proposed fix

The Scrum Team has all the skills to create an Increment by the end of every Sprint.

Every member of the Scrum Team is able to perform every task.

There are no conflicts within the Scrum Team.

A few of the Developers pair program and do Test-Driven Development.

Additions features in a usable state that complement those delivered in previous iterations

UML diagrams that describe how to deliver functionality in future iterations

A new user interface design for functionality delivered in previous iterations

An automated test suite to verify functionality delivered in previous iterations

A decomposition of all product backlog items into tasks for future sprint backlog lists

When the Product Owner says it is ready.

At the end of Sprint Planning.

When the Scrum Team agrees it is precise enough.

When the Product Backlog Refinement timebox expires.

The Scrum Master.

The Product Owner.

Quality Assurance Specialists.

The Developers.

Team manager

Project manager

Requirements engineer

Mediator for the developers and customers

Value optimizer

Scrum is a framework for developing and sustaining complex products.

Each component of scrum serves a specific purpose and is essential to Scrum's success

Scrum is based on empirical process control

Scrum is like traditional project management, but then with project managers replaced by self-management.

Scrum is a methodology based on empirical process control.

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

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

Delay test activities until a feature has been coded.

Define acceptance criteria for features.

Identify tools and techniques to be used in testing the product.

Create a plan for testing the application.

To make the code more readable

To make it easy to distinguish between different software products

To communicate the identity of the developer that wrote the code

To reduce friction in a shared codebase

To ensure that orphan functions are not created