Premium Partner

0 Login Registrieren

Store 0
Bibliothek
Info
Abos
Partner

Scrum Master

Frage zuerst
Antwort zuerst
Selbsttest

0.0 (0)

Nicht sichtbar

Lernen

Nicht sichtbar

Kartei Details

Karten	65
Sprache	English
Kategorie	Informatik
Stufe	Mittelschule
Erstellt / Aktualisiert	17.09.2023 / 27.09.2023
Lizenzierung	Keine Angabe
Weblink	https://card2brain.ch/box/20230917_scrum_master
Einbinden	<iframe src="https://card2brain.ch/box/20230917_scrum_master/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

Flip-Modus

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

Yes, but only for Scrum Teams whose work has dependencies.

Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.

No, each Scrum Team stands alone

No, that is far too hard and must be done in a hardening Sprint.

When can a Development Team cancel a Sprint?

It can't. Only Product Owners can cancel Sprints

When functional expectations are not well understood.

When the Product Owner is absent too often.

When the selected Product Backlog items for the Sprint become unachievable.

When a technical dependency cannot be resolved.

Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

The Sprint Backlog.

The Sprint Goal

The release plan.

Sprint Review minutes

How should a Development Team deal with non-functional requirements?

Ensure every Increment meets them.

Make sure the release department understands these requirements, but it is not the Development Team's responsibility.

Handle them during the Integration Sprint preceding the Release Sprint.

Assign them to the lead developers on the team.

When is a Sprint over?

When the Product Owner says it is done.

When all Product Backlog items meet their definition of "Done

When all the tasks are completed

When the time-box expires.

Scrum has a role called "Project Manager".

True

False

What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

Put them on a separate list on the Scrum board, available for all to see.

Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.

Add them to the definition of "Done" so the work is taken care of every Sprint.

How much time is required after a Sprint to prepare for the next Sprint?

The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter sprints.

Enough time for the requirements for the next Sprint to be determined and documented

Enough time for the Development team to finish the testing from the last Sprint.

None. A new Sprint starts immediately following the end of the previous Sprint

All of the above are allowed depending on the situation.

4 anzeigen
16 anzeigen
32 anzeigen

Klick dich schlau.

Gemeinsam lernen - einfach und effizient.

Jetzt registrieren Zum Login

Funktionen

Abos
Bibliothek
Card Store
Mobile App

Hilfe

Info
Kontakt
Feedback
Blog

Partner

Premium Partner
Bildungspartner
Verlagspartner

Sprachen

Deutsch
Français
English

Kontakt & Feedback

AGB
Datenschutz
Urheberrecht
Impressum
Team
Kontakt