Lernkartei LaLiDa (Seite 7 von 8)

Karten	318
Lernende	64
Sprache	English
Kategorie	BWL
Stufe	Andere
Erstellt / Aktualisiert	08.06.2020 / 24.05.2024
Weblink	https://card2brain.ch/cards/20200608_lalida?max=40&offset=216
Einbinden	<iframe src="https://card2brain.ch/box/20200608_lalida/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

59.

The time-box for a Daily Scrum is?

4 hours

15 minutes

The same time of a day every day

15 minutes for a 4 week Sprint. For shorter Sprint it is usually shorter

Two minutes per person

60.

Who is responsible for tracking the remaining work of the Sprint?

The Product Owner

The Scrum Master

The Project Manager

The Development Team in consultation with the Product Owner

The Development Team

61.

Which three of the following are true about Scrum?

Scrum is like traditional process but with self-organization to replace Project Managers.

Scrum is based on empirical process control theory.

Scrum is a methodology, where you can pick and choose which parts of Scrum´s success and you usage of Scrum to develop complex projects.

Each component in Scrum serves a specific purpose, and is essential to Scrum´s success and your usage of Scrum to develope complex projects.

Scrum is a framework for developing and sustaining complex projects.

62.

The IT manager asks a Development Team for a status report describing the progress throughout the Sprint. The Development Team asks the Scrum Master for advice. The Scrum Master should:

Tell the Development Team to figure it out themselves.

Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.

Ask the Product Owner to send the manager the report.

Tell the Development Team to fit the report into the Sprint Backlog.

Create and deliver the report to the manager herself.

63.

Who is on the Scrum Team?

Project Manager

Product Owner

Development Team

Scrum Master

None of the above

64.

The Product Owner must release each Increment to production.

Whenever the production os free of defects.

To make sure the Development Team is done every Sprint.

Without exception.

When it makes sense.

65.

What does the Cone of Uncertainty show?

Hierarchy of tasks that comprise a project.

How much work remains till the end of the Sprint.

How much is known about the Product over time.

Dependencies, start time and stop times for project tasks.

66.

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

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

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

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

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

All of the above are allowed depending on the situation.

67.

When can a Development Team cancel a Sprint?

When the Product Owner is absent too often.

When functional expectations are not well understood.

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

It can´t. Only Product Owners can cancel Sprints.

When a technical dependency cannot be resolved.

68.

What happens when a Sprint is canceled? (Three answers)

If part of the work is potentially releasable, the Product Owner typically accepts it.

Any completed and "Done" Product Backlog items are reviewed.

All incomplete Product Backlog items are re-estimated and pull back on the Product Backlog.

At the Sprint Retrospective the Scrum Master determines who from the Development Team is responsible for cancelling the Sprint.

Several top Product Backlog Items are taken into the Sprint Backlog to replace the obsolete items.

69.

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

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

The Scrum Team should choose at least one high priority process improvement and places it in the Product Backlog.

The Scrum Team should choose at least one high priority process improvement and places it in the Sprint Backlog.

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

70.

The Product Owner determines how many Product Backlog items the Development Team selects for a Sprint.

True, accordingly to what was committed to the stakeholders.

True, but only after confirmation from the resource manager that the Team has enough capacity.

True

False, the Scrum Master does that.

False

71.

During a Sprint Retroperpective, for what is the Scrum Master responsible?

Prioritising the resulting action items.

Acting as a scribe to capture the Development Team´s answer.

Participating as a Scrum team member and facilitating as requested or needed.

Summarising and report the discussion to management.

72.

When is the Sprint Backlog created?

At the beginning of the Project.

Prior to the Sprint Planning meeting.

During the Sprint

During the Sprint Planning meeting

73.

What should be taken into account for the Definition of "Done"? (Two answers)

Convention, standards and guidlines of the Organization.

Definition of "Done" of the Scrum Teams working on the same Product.

Experience of the Prodct Owner.

Advice of the Scrum Master.

Definition of "Done" of other Scrum Teams working on other products.

74.

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

Handle them during the integration Sprint preceding the Release Sprint.

Male sure the release department understand there requirements, but it is not the Development Team´s responsibility.

Assign them to the lead developers on the team.

Ensure every Increment meets them.

75.

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

Whenever a team member can accommodate more work.

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

During the Daily Scrum.

At the Sprint Planning meeting.

76.

Which are the properties of the Daily Scrum? (Two answers)

It consists of the Scrum Master asking the Team member the three questions.

It is held first thing in the morning.

It is free from and designed to promote conversation.

It is fifteen minutes or less in duration.

It is location and time remain constant.

77.

Which three of the following are feedback loops in Scrum?

Refinement Meeting

Release Planning

Daily Scrum

Sprint Retrospective

Sprint Review

78.

A Sprint Retrospective should be held:

Only when the Scrum Team determines it needs one.

At the end of the last Sprint in a project or a release.

At the beginning of each Sprint.

At the end of each Sprint.

79.

Which of the following is true about the length of the Sprint? (Two answers)

The length of the Sprint should be proportional to the work that is done in between Sprints.

It is best to have Sprints of consistent length throughout a development effort.

Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.

All Sprints must be 1 month or less.

Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.

80.

Who is responsible for engaging the stakeholder?

The Developer Team

The Business Analyst

The Team Manager

The Project Manager

The Product Owner

1.

The Product Backlog is ordered by:

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 are at the bottom.

By the Product Owner with the most valuable items placed at the top.

2.

When might a Sprint be abnormally canceled?

When the Sprint Goal becomes obsolete.

When it becomes clear that not everything will be finished by the end of the sprint.

When the Development Team feels that the work is too hard.

When the sales department has an important new opportunity.

3.

The Product Owner is not collaborating with the Development Team during the sprint. What are two valuable actions for a Scrum Master to take?

Nominate a proxy Product Owner.

Bring up the problem in the Sprint Retrospective.

Stop the Sprint, send the Product Owner to a course and restart.

Coach the Product Owner in the value of Scrum and incremental delivery.

Inform the Product Owner´s functional manager.

4.

Who should know the most about the progress toward a business objective or a release?

The Scrum Master

The Product Owner

The Project Manager

The Development Team

5.

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

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

No, each Scrum Team stands alone.

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

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

6.

The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do?

Add the item to the next Sprint.

Inform the Product Owner so he/she can work with the CEO.

Add the item to the current Sprint and drop an item of equal size.

Add the item to the current Sprint without adjustments.

7.

How is management external to the Scrum Team involved in the Daily Scrum?

The Product Owner represents their options.

The Development Team self-manages and is the only management required at the Daily.

The Scrum Master speaks on their behalf.

Management gives an update at the start of each Daily Scrum.

8.

What is the time-box for the Sprint Planning meeting?

8 hours for a monthly Sprint

4 hours for a monthly Sprint

Whenever it is done

Monthly

9.

Which three of the following are true about Scrum?

Scrum is like traditional process but with self-organization to replace Project Managers.

Scrum is methodology, where you can pick and choose which parts of Scrum you think will work for you environment.

Each component of Scrum serves a specific purpose, and is essential to Scrum´s success and your usage of Scrum to develop complex products.

Scrum is a framework for developing and sustaining complex product.

Scrum is based on empirical process control theory.

10.

Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?

Act as a go-between for them.

Monitoring communications between them and facilitate direct collaboration.

Teach the Product Owner about the technologies employed during the Sprint.

Teach the Development Team to talk in items of business needs and objectives.

11.

Which of these may a Development Team deliver at the end of a Sprint?

An increment of working software that is "Done".

A single document, if that is what the Scrum Master asked for.

Failing unit tests, to identify acceptance tests for the next Sprint.

An increment of software with minor known bugs in it.

12.

What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Development Teams?

Ask the Product Owner to assign the people to teams.

Create teams based on their skills across multiple layers (such as databases, UI, etc.)

Ask the developers to divide themselves into teams

13.

Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Three answers)

Economic Value Added

Courage

Focus

Earned value

Respect

14.

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

The Project Manager

The Scrum Team

The Development Team

The Product Owner

15.

What is the time-box for the Sprint Review?

1 day

4 hours for a monthly sprint

2 hours for a monthly sprint

4 hours or longer as needed

As long as needed

16.

Why does a Development Team need a Sprint Goal?

The Development Team is more focused with a common yet specific goal.

Sprint Goal are not valuable. Everything is known from the Product Backlog.

A Sprint Goal only gives purpose to Sprint 0.

A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.

17.

If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?

The evolution of the cost spent on the project.

When alt work will be completed so the Scrum Team can be released for other work.

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

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

18.

Every Scrum Team must have a Product Owner and Scrum Master.

False. A Scrum Master is only required when asked for by the Development Team.

True. Each must be 100% dedicated to the Scrum Team.

True. Outcomes are affected by their participation and availability.

False. A Product Owner can be replaced by a business analyst in the Development Team.

LaLiDa

Lernkarteien erstellen oder kopieren

Lernkarteien erstellen oder kopieren

Melde dich an, um alle Karten zu sehen.

SWITCHaai

Office 365

Edulog

Apple ID

Google