Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

CSM Prep > Scrum Artifacts > Flashcards

Scrum Artifacts Flashcards

1
Q

Who has the final say on the order of the Product Backlog?
1. Scrum Master
2. Product Owner
3. The Developers
4. The CEO
5. The Stakeholders

A

2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

For the purpose of transparency, when does Scrum say a new increment must be available?
1. When the PO asks to create one
2. After the AC testing phase
3. Every 3 Sprints
4. Before the release Sprint
5. At the end of every Sprint

A

5

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the characteristics of a Product Backlog Item that is “Ready” for selection in a Sprint Planning? Select three.
1. Can be implemented within one Sprint and tested in the next Sprint
2. Can be “Done” within one Sprint.
3. Somewhere at the bottom of the Product Backlog
4. Well-refined
5. Somewhere at the top of the Product Backlog
6. Has less detail

A

2,4 & 5

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

During the Sprint, if work is required, the Devs can add it to the current Sprint Backlog
True
False

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Who must ensure the new increments meet the Definition of Done?
1. Scrum Master
2. Product Owner
3. Devs
4. Scrum Team
5. QA Specialists

A

3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

When is it most appropriate for Devs to change the Definition of Done?
1. During the Sprint Retro
2. During Sprint Planning
3. Prior to starting a new Sprint
4. Prior to starting a new Project

A

1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

A scrum Team crafts the following Sprint Goal: “All the Sprint code should have passed 100% automated unit tests”.
1. Not an appropriate goal, since the Sprint Goal should be about the expected business value
2. It is a well-formed Sprint Goal
3. It is incorrect, since the Product Owner formulates the goal and not the Scrum Team

A

1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Which of the following are NOT Scrum Artifacts? Select all applicable answers.
1. The list of removed impediments
2. Product Backlog
3. Sprint Goal
4. Increment
5. Sprint Backlog

A

1 & 3

Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact.

The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scrum’s artifacts are designed to maximize the Developers’ velocity.
* True
* False

A

False

Scrum’s artifacts represent work or value. They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation.

Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:

● For the Product Backlog it is the Product Goal.
● For the Sprint Backlog it is the Sprint Goal.
● For the Increment it is the Definition of Done.

These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their stakeholders.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Which of the following is not a Scrum Artifact?
1. User Stories
2. Sprint Backlog
3. Product Backlog
4. Software Increment

A

1

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How should items in the Product Backlog be ordered?
1. Alpha first and then by list order in the Product Backlog
2. Grouped by business features first and the chronologically by date of the original business request
3. Prioritized by business importance. The items that result in the biggest ROI must be prioritized first.
4. Chronologically by date of the original business request and then by list order in the Product Backlog.

A

3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

H

Under what circumstances should the Product Backlog by reprioritized?
1. The Scrum Master should reprioritize the Product Backlog only at the end of a Sprint
2. The Scrum Master should reprioritize the Product Backlog only at the start of a new Sprint.
3. The Team should reprioritize the Product Backlog only at the end of a Sprint.
4. The PO should reprioritize the Product Backlog whenever new information is learned.

A

4

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The individual, detailed pieces of work that are needed to convert a product backlog item into a working software component or solution are called:
1. User Stories
2. Use Cases
3. Line Items
4. Tasks

A

4

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Which of the following Statements best describes the Product Backlog items?
1. Undefined or poorly defined items should be placed in the Product Backlog with a low priority
2. All Product Backlog items are the result of a(n) analysis, requirements and/or design phase(s).
3. Undefined or poorly defined items should be kept out of the Product Backlog until sufficient details is available.
4. Every Product Backlog item, low or high priority, should possess sufficient detail for the Team to complete in a Sprint.

A

3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What Artifact shows actual versus planned work?
1. Work Flow
2. Burn down Chart
3. Task Breakdown
4. Stakeholders

A

2

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

??? constitute the Sprint Backlog and are often estimated in hours
1. User Stories
2. Use Cases
3. Features
4. Tasks

A

4

In Scrum, a “task” typically refers to a specific unit of work that needs to be completed as part of implementing a user story during a sprint. Tasks are more granular than user stories and are often used by development teams to break down the work required to deliver a user story into manageable pieces.

17
Q

Under what circumstances should separate Product Backlogs be maintained?
1. There are several PO for one one product. Each PO should have their own Backlog.
2. There are multiple teams working on independent products. Each unique combination of team and product should have an independent Product Backlog.
3. There are multiple features being worked on by the same team.
4. There are multiple teams working on components of the same product. Each team should have an independent Product Backlog.

A

2

18
Q

What is the maximum amount of time a Sprint Retro should take?
1. 1 hour
2. 1 and a half hours
3. 3 hours for a 30 day Sprint.
4. 8 hours for a 30 day Sprint

A

3

19
Q

What is the major difference between the Product Backlog and the Sprint Backlog?
1. The PB is the same as the Sprint Backlog
2. The PB is a subset of the Sprint Backlog
3. The Sprint Backlog is a subset of the PB
4. The Sprint Backlog is owned by the Product Owner.

A

3

20
Q

What does the Sprint Backlog Include?
1. Just user stories
2. Use Cases
3. Selected Backlog Items and Tasks
4. Test Cases

A

3

21
Q

What is produced by the Dev Team at the end of a Sprint?
1. A potentially releasable product
2. The whole, releasable product
3. A product progress update
4. A new folder structure for the product versioning files

A

1

22
Q

How big i a Product Backlog?
1. As big as it needs to be
2. It has a max of 100 items
3. It has 100 items per Dev Team member
4. As big as the number of sticky-notes available

A

1

23
Q

How many ticketed items should a Sprint Backlog hold?
1. 10 per person per week of the Sprint
2. 1 for each product deliverable
3. As many as the team feels it needs
4. Enough for each member of the team

A

3

24
Q

When can a Sprint Backlog be changed?
1. After the first week - team needs to set enough time to see what is not going to get done
2. Whenever something needs to be changed
3. Only after the first day
4. Only during Sprint Planning -

A

2

25
Q

What is the Defintion of Done?
1. Varies, depending upon the Scrum Team but everyone agrees to a definition.
2. When a check box can be checked.
3. When a product meets an excellent standard.
4. It’s defined in the Scrum Guide.

A

1

26
Q

What is the refinement process?
1. A way of making sure the Product Backlog items properly reflect the work needed.
2. A way of getting extracted mineral into a useable form.
3. A way to make sure Sprint Backlog items properly reflect the work needed
4. All of the above.

A

1

Only focused on the Product Backlog.

27
Q

What can the Sprint Backlog enable?
1. A real-time view of the working taking place in the Sprint.
2. The Product
3. The Product Backlog
4. All of the above

A

1

28
Q

What might cause changes to a Product Backlog?
1. New features being requested of the Product
2. The refinement process
3. Issue being reported about the product
4. All of the above.

A

4

29
Q

What does the Product Backlog describe?
1. All the features of a Product.
2. All of the upcoming work on a project.
3. To-do items that the Product Owner needs to organize.
4. It describes the wants and needs of the org.

A

1

30
Q

What three factors are the trio of constraints to release management?
1. Budget, Time & Scope
2. Team members, time and scope
3. Budget, time and training
4. Resources, Time and Scale

A

1

31
Q

Which of these are the attributes of a quality Backlog?
1. Prioritized
2. Forecasted
3. Dynamic
4. All of the above

A

4

Other attributes are: Fit for Purpose, Correct Level of Detail & Collaborative Input.

32
Q

What is a DEEP product backlog?
1. Detailed Appropriately, Emant, Estimated & Prioritized.
2. Detailed Appropriately, Emergent, Elegant & Prioritized.
3. Detailed Appropriately, Emergent, Estimated and Prioritized.
4. Detailed Adequately, Emergent, Estimated & Prioritized

A

3

DEEP is an acronym often used to describe desirable characteristics of a well-maintained Product Backlog in Scrum. It stands for Detailed Appropriately, Emergent, Estimated, and Prioritized.

Maintaining a DEEP Product Backlog is crucial for the success of the Scrum framework. It helps in providing clarity, adaptability, and transparency, which are key aspects of effective Agile development. The Product Owner is primarily responsible for ensuring that the Product Backlog is DEEP, working with stakeholders and the development team to refine and adjust it as needed.

33
Q

When multiple Scrum Teams are working on same project, what best describes the Definition of Done?
1. Each team uses its own but must make it clear to the other teams.
2. All Scrum Teams must mutally define and comply with the same DoD.
3. Each team defines and uses its own.
4. It depends

A

2

34
Q

The Product Goal is in the Product Backlog.
True
False

A

True

The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.

A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.

The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.

35
Q

Which two statements explain why the Definition of Done is important to the Scrum Team? (Choose the two best answers)
1. It identifies undone work that can be addressed in a separate Sprint.
2. It helps the Scrum Team track the open work during a Sprint.
3. It creates Transparency regarding progress within the Scrum.
4. It assures that the Increment reviewed at the Sprint Review is usable so the Scrum team can chose to release it.

A

3 & 4

The Scrum Guide™ of 2020 says :

” The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.

The moment a Product Backlog item meets the Definition of Done, an Increment is born.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.

If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. “

36
Q

What two attributes are optional for a Product Backlog Item?
1. Order
2. Dependencies
3. Size Estimate
4. Test descriptions that will prove PB item completeness when “Done.”
5. Description

A

2 & 4

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order and estimate.

37
Q

All items of the Product Backlog must be written by the Product Owner before being given to the Developers.
True
False

A

False

Explanation
The Product Owner is responsible for the Product Backlog. Who adds the items and how they are added to the Product Backlog vary widely across organizations, Scrum Teams, and individuals.

“Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.”

38
Q

The Product Owner wants to apply some non-functional requirements to the Product. What is the best way to proceed?
1. Create a new item for every requirement in the Product Backlog.
2. Add the non-functional requirements to the DoD & check every increment against these requirements.
3. Find a way to convert non-functional requiremetns into Product features and act accordingly.

A

2

Non-functional requirements describe qualities of the Product being developed. For example, the Product should be secure and extensible. The only way to meet such requirements is to have them as a part of the DoD and check every Increment against these criteria.

As Scrum Teams mature, it is expected that their definitions of “Done” will expand to include more stringent criteria for higher quality. New definitions, as used, may uncover work to be done in previously “Done” increments. Any one product or system should have a definition of “Done” that is a standard for any work done on it.

39
Q

What does Product Backlog management include? Select the three most applicable answers.
1. Ensuring that the Product Backlog is visible, transparent & clear to all, & shows what the Scrum Team will work on next.
2. Ordering items in the Product Backlog to best achieve goals and missions.
3. Optimizing the value of the work the Developers perform.
4. Moving the Product Backlog items into the Sprint Backlog
5. Presenting Product Backlog items to the Key Stakeholders

A

1,2 & 3

CSM Prep (5 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions