Set of flashcards LaLiDa (Page 2 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>

41.

The "cone of uncertainty" can be used to do that? (One answer)

Determine the cost of a project before it is begun.

Project what will be complete by a given Sprint.

Determine whether to cut quality, similar to the "Iron Triangle" of software development.

Illustrate that, as a forecast lengthens, it is increasingly less certain.

42.

A Product Owner can measure success by an increase in the team´s velocity.

True

False

43.

Which of these may a Development Team deliver at the end of a Sprint? (One answer)

An increment of working software that is "done".

An increment of software with minor known bugs in it.

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

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

44.

Software dependencies could influence how the Product Owner orders Product Backlog items.

True

False

45.

The Product Owner makes sure the right stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.

True

False

46.

Which three of the following are feedback loops in Scrum?

Daily Scrum

Sprint Review

Release Planning

Sprint Retroperspective

Refinement Meeting

47.

There are multiple teams working on one product. Each team should have a separate Product Owner.

True

False

48.

What is the recommended size for a Development Team? (One answer)

At least 7

3 to 9

7 plus or minus 3

9

49.

What is Product Owner work that a Product Owner might delegate? (One Answer)

Writing User Stories.

Ordering the Product Backlog.

Representing stakeholders to the Scrum team.

Attending the Sprint Review.

50.

Which is NOT a valid consideration when ordering a Product Backlog? (One answer)

Alignment with business strategy and goals.

Risk.

Importance to customers.

Development Team tools and techniques.

Dependencies on other Product Backlog items.

51.

What is typical for a Product Owner in a Sprint? (Two answers)

Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items.

Update the work plan for the Development Team on a daily basis.

Work with the Development Team on Product Backlog refinement.

Create financial reporting upon the spent hours reported by the Development Team.

Collaborate with stakeholders, user communities and product managers.

52.

During the Sprint Review, it is up to the stakeholders to reorder the Product Backlog.

True

False

53.

Which three of the following are timeboxed events in Scrum? (Three answer)

Sprint Retroperspective

Release Testing

Daily Scrum

Release Retrospective

Sprint Planning

54.

A product´s success is measured by: (Three answer)

The impact on customer satisfaction.

The delivery of upfront defined scope compared to the upfront planned time.

The impact on revenue.

The impact on cost.

The impact on my performance rating.

55.

Which statement best describes the Sprint Backlog as outcome of the Sprint Planning? (One Answer)

It is a complete list of all work to be done in a Sprint.

Each task is estimated in hours.

It is the Development Team´s plan for the Sprint.

Every time has a designated owner.

It is ordered by the Product Owner.

56.

A product Increment must be released to production at the end of each Sprint.

True

False

57.

When a Development Team determines that it will not be able to finish the complete forecast, who hast to be present when reviewing and adjusting the Sprint work selected? (One answer)

The Scrum Master, project manager and Development Team.

The Product Owner and the Development Team.

The Product Owner and all stakeholders.

The Development Team.

58.

The length of a Sprint should be: (One answer)

Short enough to keep business riskacceptable to the Procut Owner.

Short enough to be able to synchronise the development work with other business events.

No more than one calendar month.

All of these answers are correct.

59.

A Development Team is required to deliver a done Increment by the end of a Sprint. Select two statements that explain what "Done" means. (Two answers)

No work left from the definition of "Done".

Ready for integration.

Als work to create software that is ready to be released to end users.

Whatever the Product Owner defines as quality.

Als work the Development Team is willing to do.

60.

Who is on the Scrum Team? (All that apply)

Scrum Team

Product Owner

Development Team

Project Manager

None of the above

61.

When should the Product Backlog be refined? (Two answer)

The Product Owner and the Development Team do it in the 1-2 preceding Sprint.

The Product Owner takes the time between the Sprint to do it.

The Product Owner must do this essential work in Sprint 0.

The Product Owner and the Development Team do it in the actual Sprint if they haven´t been able to do it in preceding Sprints.

Business analysts in the organisation should do this work for the Scrum Team 1-2 Sprints ahead of the development Sprint.

When might a Sprint be abnormally canceled? (One answer)

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 sates department has an important new opportunity.

When the Sprint Goal becomes obsolete.

63.

What are two responsibilities of testers in a Development Team? (Two answer)

Scrum has no "tester" role.

Finding bugs.

Verifying the work of programmers.

Tracking quality metrics.

Everyone in the Development Team is responsible for quality.

64.

What activities would a Product Owner typically undertake in the phase between the end of the current Sprint and the start of the next Sprint? (One answer)

Refine the Product Backlog.

Update the project plan with stakeholders.

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

65.

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

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 stakeholder) may not be able to accurately inspect what is done.

66.

A Scrum Team has been working on a product for 9 Sprints. A new Product Owner comes in understanding he is accountable for Product Backlog. However, he is unsure about the purpose of the Product Backlog. He´s read that the Product Backlog should be a list of all user features for the product. He goes to the Scrum Master skin where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?

Stability requirements
Performance requirements
Product Funktionality
Documentation
Fixes

Yes, they all belong on the Product Backlog. Product Backlog is supposed to be the "single source of truth" for all the work for the product.

No. Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholder. Other types of requirements should be managed separately by the Development Team. They are not the Product Owner´s concern.

67.

The Product Owner must write all of the Product Backlog (e.g. user stories. non-functional requirements, etc.) on the Product Backlog before handing them over to the Development Team.

True

False

68.

The top priority items of the Product Backlog should be analyzed, estimated and prioritized adequately to begin a Sprint. This is referred to as an actionable, or "Ready", Product Backlog. At the start of the Sprint Planning meeting, select the best description of the Product Backlog items that the Product Owner wants to have done. (One answer)

They are started as User Stories and cannot be epics.

They are stated as User Stories or use case and test cases must have been identified for acceptance.

They are clearly stated, refined and understood by the Product Owner and the Development Team such that forecast of items can be made to implement the Sprint Goal.

They are fully described as User Stories or use cases already decomposed into task that will require no more than one-person day to complete by the Development Team.

69.

Which answer best describes the topic covered in Sprint Planning? (One answer)

What can be done and how to do it.

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

What to do and who will do it.

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

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

70.

Who is reponsible for coping with incomplete artifact transparency? (one Answer)

The Scrum Team

The Development Team

The Product Owner

The Scrum Master

73.

When should a Sprint Goal be created? (One answer)

At any time during the Sprint.

It must be established before Sprint Planning in order to begin planning.

During Sprint Planning.

A Sprint Goal is not mandatory in Scrum.

It should have been created in the previous Sprint during Product Backlog refinement.

74.

The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.

True

False

75.

Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do? (Select the best option)

Assign a responsibility team member for at least one improvement. Check the progress at the next Retrospective.

Make sure the Sprint Backlog for the next Sprint included at least one high priority process improvement.

Make sure the Sprint Backlog for the next Sprint includes all the improvements.

Assign responsible team members for every improvement. Check the progress at the next Retrospective.

76.

The Product Owner must use: (Choose all that apply)

Release burndown diagram.

Burndown chart.

Feature burn-up.

Critical Path Analysis.

None of the above.

A done Increment is valuable if: (Two answer)

It is likely to increase cutomer satisfaction.

It meets the business analyst´s specifications.

It is delivered when the Product Owner expected it.

It reduces long-term operational costs.

It has all the features that the Product wanted in a Sprint.

78.

The Product Owner must release each Increment to production. (One answer)

Without exception.

When it makes sense.

Whenever the product is free of defects.

To make sure the Development Team is done eery Sprint.

79.

A Product Backlog is: (Three answer)

An inventory of things to be done for the Product.

Ordered based on priority, value, dependencies and risk.

An exhaustive list of upfront approved requirements to be implemented for the system.

Managed by the Product Owner.

Only visible to the Product Owner stakeholder.

80.

A Product Owner with multiple teams working on one product should maintain a separate Product Backlogs for each team.

True

False

1.

Which Scrum artifacts are prioritized?

Both the Product Backlog and Sprint Backlog.

Only the Product Backlog.

Only the Sprint Backlog.

None.

2.

Who owns the Product Backlog?

The Development Team

The Product Owner

The Scrum Master

The Scrum Team

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