Set of flashcards LaLiDa (Page 6 of 8)

Flashcards	318
Students	64
Language	English
Category	Micro-Economics
Level	Other
Created / Updated	08.06.2020 / 24.05.2024
Weblink	https://card2brain.ch/box/20200608_lalida
Embed	<iframe src="https://card2brain.ch/box/20200608_lalida/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>

43.

What happens during the Sprint? (Three answers)

No changes are made that would endanger the Sprint Goal.

Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

Quality goals do not decrease.

Sprint scope is defined at the Sprint Planning and cannot be changed.

The Sprint Goal is changed frequently to reflect the status of the remaining work.

44.

A properly functioning Scrum Team will have at least one Release Sprint and may well have several.

True

False

45.

How frequently should Scrum users inspect Scrum artifacts and progress toward a Sprint Goal?

Frequently, but it should not get in the way of the work.

As frequently as possible

After the Daily Scrum

At the Sprint Review

46.

Five 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 other teams. What should the Scrum Master do?

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

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

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

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.

47.

The purpose of a Sprint is to produce a done Increment of product.

True

False

48.

A Scrum Team has been working on a Product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog. However, he is unsure about his responsibilities.
Which two activities are part of the Product Owner rote according to Scrum?

Prociding the Development Team with detailed specification

Describing features as use cases

Creating detailed functional test cases

Ensuring that the most valuable functionality is produced first, at all times

Interacting with stakeholders.

49.

Which Scrum value is affected by a lack of trust in the Scrum Team?

Openness

Respect

Focus

Courage

All of the above

50.

Multiple Scrum Teams working on the same product or system all select work from the same Product Backlog.

True

False

51.

Which answer best describes the topics covered in Sprint Planning?

How conditions have changed and how the Product Backlog should evolve.

Who is on the team and what team member roles will be.

What went wrong in the last Sprint and what to do differently this Sprint.

What can be done and how to do it.

What to do and who will do it.

52.

What is the order of items in the Product Backlog?

Less valuable and most unclear items at the bottom.

The less clear items at the top.

Alphabetical.

The recently added items at the top.

53.

A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example set up conference calls) before the Daily Scrum. What action should the Scrum Master take?

Setup the meeting and tell the Development Team that is how it will be done.

Inform management and ask them to solve it.

Allow the Development Team to self manage and determine for itself what to do.

Ask the Development Team members to alternate who is responsible for meeting setup.

54.

When a Development Team is having trouble delivering a working Increment because they don´t understand a functional requirement, what should they do?

Add a specialist to the Development Team.

Collaborate with the Product Owner to determine what is possible and acceptable.

Defer the work to a more appropriate Sprint.

Partially complete the functionality, and discuss the remaining work at the Sprint Review.

55.

The Development Team should have all the skills needed to:

Turn Product Backlog items into an Increment of potentially releasable product functionality.

Do all of the development work, except for specialised testing that requires additional tools and environments.

Complete the project within the date and cost as calculated by the Product Owner.

56.

What activities would a Product Owner typically undertake in the time between the end of the current Sprint and the start of the next Sprint?

Refine the Product Backlog.

Update the project plan with stakeholders.

Work with the OA departments on the Increment of the current Sprint.

There are no such activities. The next Sprint starts immediately after the current Sprint.

57.

What are the three questions the Scrum Guide gives as an example that can be used at the Daily Scrum?

Do I have complete understanding of the Sprint Backlog item I am working on?

Did I explain all the discovered issue I found yesterday to the Product Owner?

Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

What will I do today to help the Development Team meet the Sprint Goal?

What did I do yesterday that helped the Development Team meet the Sprint Goal?

58.

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?

By facilitating Development Team decisions.

By removing impediments that hinder the Development Team.

By keeping high value features high in the Product Backlog.

By ensuring the meeting start and end at the proper time.

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.

LaLiDa

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