Premium Partner

0 Login Registrieren

Store 0
Bibliothek
Info
Abos
Partner

ITIL 3.0

Frage zuerst
Antwort zuerst
Selbsttest

0.0 (0)

Nicht sichtbar

Lernen

Nicht sichtbar

Kartei Details

Karten	67
Sprache	Deutsch
Kategorie	Informatik
Stufe	Andere
Erstellt / Aktualisiert	29.11.2022 / 29.11.2022
Lizenzierung	Keine Angabe
Weblink	https://card2brain.ch/box/20221129_itil_3_0
Einbinden	<iframe src="https://card2brain.ch/box/20221129_itil_3_0/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

Flip-Modus

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.

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

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.

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

The Scrum Team with the highest velocity pulls Product Backlog items first

The Development Teams pull in work in agreement with the Product Owner

The Product Owner should provide each team with its own Product Backlog

Each Scrum Team takes an equal numbers of items.

The Product Owner decides.

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.

Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

The Project Manager

The Product Owner

The Scrum Master

The Development Team

All of the above

The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days?
(Choose three.)

Opportunities to inspect and adapt the Sprint Backlog are lost

Impediments are raised and resolved more slowly.

The Product Owner cannot accurately report progress to the stakeholders

Too much work is spent updating the Scrum board before the meeting

The Sprint plan may become inaccurate

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