Lernkartei SCRUM

Karten	146
Sprache	English
Kategorie	Technik
Stufe	Universität
Erstellt / Aktualisiert	04.04.2023 / 03.05.2024
Weblink	https://card2brain.ch/box/20230404_scrum
Einbinden	<iframe src="https://card2brain.ch/box/20230404_scrum/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

Who creates the definition of "Done"?

The Scrum Master as he/she is responsible for the Development Team’s productivity.

The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.

The Product Owner as he/she is responsible for the product’s success.

The development organization (or Development Team if none is available from the development organization).

The Scrum Master as he/she is responsible for the Development Team’s productivity.

The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.

The Product Owner as he/she is responsible for the product’s success.

The development organization (or Development Team if none is available from the development organization).

Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the order teams. What should the Scrum Master do?

Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint.

Teach them that it is their responsibility to work with the other teams to create an integrated increment.

Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.

Visit the five teams each day to inspect that their Sprint Backlogs are aligned.

Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint.

Teach them that it is their responsibility to work with the other teams to create an integrated increment.

Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.

Visit the five teams each day to inspect that their Sprint Backlogs are aligned.

Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

The Project Manager.

The Development Team.

The Scrum Team.

The Product Owner.

The Project Manager.

The Development Team.

The Scrum Team.

The Product Owner.

When do Development Team members take ownership of a Sprint Backlog item?

At the Sprint planning meeting.

During the Daily Scrum.

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual Development Team member.

Whenever a team member can accommodate more work.

At the Sprint planning meeting.

During the Daily Scrum.

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual Development Team member.

Whenever a team member can accommodate more work.

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 responsibilit

Handle them during the Integration Sprint preceding the Release Sprint.

Assign them to the lead developers on the team.

Ensure every Increment meets them.

Make sure the release department understands these requirements, but it is not the Development Team’s responsibilit

Handle them during the Integration Sprint preceding the Release Sprint.

Assign them to the lead developers on the team.

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.

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.

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

The Sprint Backlog

The Sprint Goal

The release plan

Sprint Review minutes

In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams? (Choose the best answer.)

Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.

It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.

Check with the allocation department to see who has worked together before and make these the first teams.

Create a matrix of skills, seniority, and level of experience to assign people to teams.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.

It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.

Check with the allocation department to see who has worked together before and make these the first teams.

Create a matrix of skills, seniority, and level of experience to assign people to teams.

User documentation is part of your definition of "Done". However, there aren’t enough technical writers for all teams. Your Development Team doesn’t have a technical writer. What should you do?

Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.

Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.

Wait until you have a technical writer on your Development Team to take care of this.

Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.

Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.

Wait until you have a technical writer on your Development Team to take care of this.

Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.

You are the Scrum Master for four Scrum Teams working from the same Product Backlog. Several of the developers come to you complaining that work identified for the upcoming two Sprints will require full-time commitment from a technical specialist who is external to the teams. What are two key concerns for the Scrum Master to take into account in this situation? (Choose two.)

The desire to maintain a stable velocity.

The benefit of Development Teams figuring out a solution for themselves.

The need to have enough work to keep all Development Team members busy.

The ability of the Development Teams to produce integrated Increments.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The desire to maintain a stable velocity.

The benefit of Development Teams figuring out a solution for themselves.

The need to have enough work to keep all Development Team members busy.

The ability of the Development Teams to produce integrated Increments.

The Product Backlog is ordered by:

The Product Owner with the most valuable items placed at the top

Risk, where safer items are at the top, and riskier items are at the bottom

Items are randomly arranged

Size, where small items are at the top and large items are at the bottom.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The Product Owner with the most valuable items placed at the top

Risk, where safer items are at the top, and riskier items are at the bottom

Items are randomly arranged

Size, where small items are at the top and large items are at the bottom.

What happens if the Development Team cannot complete its work by the end of the Sprint?

The Sprint is extended and future Sprints use this new duration.

The Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length.

The Sprint is extended temporarily. Lessons are taken to ensure it doesn’t happen again.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The Sprint is extended and future Sprints use this new duration.

The Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length.

The Sprint is extended temporarily. Lessons are taken to ensure it doesn’t happen again.

Which topics should be discussed in the Sprint Review?

The Scrum process, and how it was used during the Sprint.

Coding and engineering practices.

Sprint results.

All of the above.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The Scrum process, and how it was used during the Sprint.

Coding and engineering practices.

Sprint results.

All of the above.

What does it mean for a Development Team to be cross-functional?

The Development Team includes not only developers but also business analysts, architects, and testers.

The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software.

Developers on the Development Team work closely with business analysts, architects, developers and testers who are not on the team.

The Development Team is a virtual team drawing from separate teams of business analysts, architects, developers and testers.

Commandes clavier:

= tourner,

= avant/arrière,

= faire défiler

The Development Team includes not only developers but also business analysts, architects, and testers.

The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software.

Developers on the Development Team work closely with business analysts, architects, developers and testers who are not on the team.

The Development Team is a virtual team drawing from separate teams of business analysts, architects, developers and testers.

Sprint burndown charts are an efficient tracking tool, because they show:

An estimate of the total work remaining for the Sprint.

How much effort has gone into a Sprint.

How many hours have been worked by each Development Team member.

How many Product Backlog items remain.

An estimate of the total work remaining for the Sprint.

How much effort has gone into a Sprint.

How many hours have been worked by each Development Team member.

How many Product Backlog items remain.

How much work must a Development Team do to a Product Backlog item it selects for a Sprint?

A proportional amount of time on analysis, design, programming, testing, and documentation.

As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.

All development work and at least some testing.

As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done".

A proportional amount of time on analysis, design, programming, testing, and documentation.

As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.

All development work and at least some testing.

As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done".

If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate? (Choose the best answer.)

The evolution of the cost spent on the project

When all work will be completed to the Scrum Team can be released for other work.

When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.

When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.

The evolution of the cost spent on the project

When all work will be completed to the Scrum Team can be released for other work.

When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.

When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added.

SCRUM

Lernkarteien erstellen oder kopieren

Lernkarteien erstellen oder kopieren

Melde dich an, um alle Karten zu sehen.

SWITCHaai

Office 365

Edulog

Apple ID

Google