Set of flashcards ITIL 3.0

Flashcards	67
Language	Deutsch
Category	Computer Science
Level	Other
Created / Updated	29.11.2022 / 29.11.2022
Weblink	https://card2brain.ch/box/20221129_itil_3_0
Embed	<iframe src="https://card2brain.ch/box/20221129_itil_3_0/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

What is the recommended size for a Scrum Team? (Choose the best answer.)

At least 7

9

10 or fewer

7 plus or minus 3

At least 7

9

10 or fewer

7 plus or minus 3

When must a Product Owner release each Increment? (Choose the best answer.)

When it makes sense

When the Scrum Team finishes their work

Whenever the product is free of defects

After every Sprint, Without exception

When it makes sense

When the Scrum Team finishes their work

Whenever the product is free of defects

After every Sprint, Without exception

What techniques could the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply? (Choose the best two answers.)

Involve the complete Scrum Team in making a decision

Use coaching techniques; such as open questions and active listening

Ask an external agile coach what they recommend

Ask team members to take the issue up with to the company's Human Resources department

Involve the complete Scrum Team in making a decision

Use coaching techniques; such as open questions and active listening

Ask an external agile coach what they recommend

Ask team members to take the issue up with to the company's Human Resources department

During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate?

(Choose the best answer.)

The Scrum Team may add items to the Sprint Backlog for the next Sprint.

The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog

The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly

The Scrum Master selects the most important process improvement and places it in the Sprint Backlog

The Scrum Team may add items to the Sprint Backlog for the next Sprint.

The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog

The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly

The Scrum Master selects the most important process improvement and places it in the Sprint Backlog

When many Scrum Teams are working on a single product, what best describes the Definition of Done? (Choose the best answer.)

Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint

The Scrum Masters from each Scrum Team define a common Definition of Done

Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known

All Scrum Teams must have a Definition of Done that makes their combined work potentially releasable

Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint

The Scrum Masters from each Scrum Team define a common Definition of Done

Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known

All Scrum Teams must have a Definition of Done that makes their combined work potentially releasable

Who is accountable for tracking the remaining work toward the Sprint Goal? (Choose the best answer.)

The Developers

The Scrum Master

The Product Owner

The Project Manager

The Developers

The Scrum Master

The Product Owner

The Project Manager

Which approach is best for Scrum Teams in order to produce valuable Increments? (Choose the best answer.)

Each Developer works on the component where they feel that they can contribute

Each Scrum Team is accountable for developing functionality from beginning to end

Each Scrum Team works on an independent set of components

Each Scrum Member works only as an independent layer of the system

Each Developer works on the component where they feel that they can contribute

Each Scrum Team is accountable for developing functionality from beginning to end

Each Scrum Team works on an independent set of components

Each Scrum Member works only as an independent layer of the system

Who is accountable for clearly expressing Product Backlog items? (Choose the best answer.)

The business analyst who represents the Product Owner

The Product Owner

The Scrum Master, or the Scrum Master may have the Developers do it

The Scrum Master

The business analyst who represents the Product Owner

The Product Owner

The Scrum Master, or the Scrum Master may have the Developers do it

The Scrum Master

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?

(Choose the best answer.)

Without a new vocabulary as a reminder of the change, very little change may actually happen

The organization may not understand what has changed within Scrum and the benefits of Scrum may be lost.

Management may feel less anxious

All answers apply

Without a new vocabulary as a reminder of the change, very little change may actually happen

The organization may not understand what has changed within Scrum and the benefits of Scrum may be lost.

Management may feel less anxious

All answers apply

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

When the Product Owner identifies new work.

As soon as possible after they are identified

When the Scrum Master has time to enter them.

During the Daily Scrum after the Development Team approves them.

Keyboard commands:

= turn,

= for-/backward,

= scroll

When the Product Owner identifies new work.

As soon as possible after they are identified

When the Scrum Master has time to enter them.

During the Daily Scrum after the Development Team approves them.

What is the main reason for the Scrum Master to be at the Daily Scrum?

To gather status and progress information to report to management.

To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.

To make sure every team member answers the three questions

Keyboard commands:

= turn,

= for-/backward,

= scroll

To gather status and progress information to report to management.

To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.

To make sure every team member answers the three questions

You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system,
i.e. one for the frontend, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it's a good idea to have teams organized by feature.

What are the advantages of keeping component teams while starting Scrum?

There's less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.

Component teams generally have the skills needed to create a working Increment of software that provides business value.

Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would

There are fewer cross-team dependencies than working in feature teams.

Keyboard commands:

= turn,

= for-/backward,

= scroll

There's less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.

Component teams generally have the skills needed to create a working Increment of software that provides business value.

Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would

There are fewer cross-team dependencies than working in feature teams.

How often should Development Team membership change?

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

Never, because it reduces productivity

As needed, with no special allowance for changes in productivity

Every Sprint to promote shared learning.

Keyboard commands:

= turn,

= for-/backward,

= scroll

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

Never, because it reduces productivity

As needed, with no special allowance for changes in productivity

Every Sprint to promote shared learning.

When is it most appropriate for a Development Team to change the definition of "Done"?

During Spring Planning

Prior to starting a new Sprint

During the Sprint Retrospective

Prior to starting a new project

Keyboard commands:

= turn,

= for-/backward,

= scroll

During Spring Planning

Prior to starting a new Sprint

During the Sprint Retrospective

Prior to starting a new project

Which statement best describes Scrum?

A defined and predictive process that conforms to the principles of Scientific Management

A complete methodology that defines how to develop software

A cookbook that defines best practices for software development

A framework within which complex products in complex environments are developed

Keyboard commands:

= turn,

= for-/backward,

= scroll

A defined and predictive process that conforms to the principles of Scientific Management

A complete methodology that defines how to develop software

A cookbook that defines best practices for software development

A framework within which complex products in complex environments are developed

Select two ways in which technical debt impacts transparency. (Choose two.)

When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.

It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint

As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways

It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt

When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.

It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint

As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways

It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt

ITIL 3.0

Create or copy sets of flashcards

Create or copy sets of flashcards

Log in to see all the cards.

SWITCHaai

Office 365

Edulog

Apple ID

Google