Scrum Artifacts

Question 1

what do scrum artifacts represent[2]?

Answer 1

• work
• value

Question 2

what are scrum artifacts designed to do?

Answer 2

maximise transparency of key information

Question 3

because the artifacts are designed to maximise transparency, everyone inspecting them as the same…?

Answer 3

basis for adaptation

Question 4

each artifact contains a commitment to ensure what?

Answer 4

it provides information that enhances transparency and focus against which progress can be measured

Question 5

each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. what is the the commitment for the product backlog?

Answer 5

the product goal

Question 6

each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. what is the commitment for the spring backlog?

Answer 6

the sprint goal

Question 7

each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. what is the commitment for the increment?

Answer 7

the definition of done

Question 8

each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured. why do these commitments exist?

Answer 8

to reinforce empiricism and the scrum values for the scrum team and their stakeholders

Question 9

scrum artifact, product backlog:
what is this?

Answer 9

an emergent, ordered list of what is needed to improve the product

Question 10

scrum artifact, product backlog:
it is the single source of work undertaken by who?

Answer 10

the scrum team

Question 11

scrum artifact, product backlog:
product backlog items that can be done by done by who within what are deemed ready for the selection in a sprint planning event?

Answer 11

that can be done by the scrum team within one sprint

Question 12

scrum artifact, product backlog:
product backlog items that can be done by the scrum team within one sprint are deemed ready for selection in a sprint planning event. they usually acquire what?

Answer 12

a degree of transparency after refining activities

Question 13

scrum artifact, product backlog:
product backlog refinement is the act of what?

Answer 13

breaking down and further defining product backlog items into smaller more precise items

Question 14

scrum artifact, product backlog:
product backlog refinement is a what kind of activity?

Answer 14

an ongoing activity

Question 15

scrum artifact, product backlog:
product backlog refinement is an ongoing activity to add details such as…[3]

Answer 15

• description
• order
• size

Question 16

scrum artifact, product backlog:
the attributes of product backlog refinement often vary with that?

Answer 16

the domain of work

Question 17

scrum artifact, product backlog:
the developers who will be doing the work are responsible for what?

Answer 17

the sizing

Question 18

scrum artifact, product backlog:
the PO may influence the developers by doing what?

Answer 18

helping them understand and select trade-offs

Question 19

scrum artifact, product backlog, commitment - product goal:
what does the product goall describe?

Answer 19

a future state of the product which can serve as a target for the scrum team to plan against

Question 20

scrum artifact, product backlog, commitment - product goal:
the product goal is in what?

Answer 20

the product backlog

Question 21

scrum artifact, product backlog, commitment - product goal:
the product goal is in the product backlog. the rest of the product backlog emerges to define…?

Answer 21

“what” will fulfil the product goal

Question 22

scrum artifact, product backlog, commitment - product goal:
what is a product(quote)

Answer 22

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

Question 23

scrum artifact, product backlog, commitment - product goal:
the product goal is the ___ ___ ___, for who?

Answer 23

the long-term objective for the scrum team

Question 24

scrum artifact, product backlog, commitment - product goal:
what must the scrum team do for one objective before moving on to the next?

Answer 24

fulfil or abandon one objective

Question 25

scrum artifact, sprint backlog: what is the sprint backlog composed of[3]?

Answer 25

- the sprint goal - why - the set of product backlog items selected for the sprint - what - an actionable plan for delivering the increment - how

Question 26

scrum artifact, sprint backlog: the sprint backlog is a plan by and for who?

Answer 26

the developers

Question 27

scrum artifact, sprint backlog: the sprint backlog is a highly ___, ___-___ picture of what?

Answer 27

highly visible, real-time picture of the work that the developers plan to accomplish during the sprint in order to achieve the sprint goal

Question 28

scrum artifact, sprint backlog: the sprint backlog is a highly visible, real-time picture of the work that the developers plan to accomplish during the sprint in order to achieve the sprint goal. consequently, as of when is the sprint backlog updated?

Answer 28

throughout the sprint as more is learned

Question 29

scrum artifact, sprint backlog: how much detail should the sprint backlog have?

Answer 29

enough that they can inspect their progress in the daily scrum

Question 30

scrum artifact, sprint backlog, commitment - sprint goal: the sprint goal is what?

Answer 30

the single objective for the sprint

Question 31

scrum artifact, sprint backlog, commitment - sprint goal: although the sprint goal is a commitment by the developers, what does it provide? in terms of what?

Answer 31

flexibility in terms of the exact work needed to achieve it

Question 32

scrum artifact, sprint backlog, commitment - sprint goal: what does the sprint goal create[2], and what does this encourage?

Answer 32

- coherence - focus - encouraging the scrum team to work together rather than on separate initiatives

Question 33

scrum artifact, sprint backlog, commitment - sprint goal: when is the sprint goal created, and what is it added to?

Answer 33

- created during the sprint planning event - added to the sprint backlog

Question 34

scrum artifact, sprint backlog, commitment - sprint goal: as the developers work during the sprint, what is kept in mind?

Answer 34

the sprint goal

Question 35

scrum artifact, sprint backlog, commitment - sprint goal: as the developers work during the sprint, they keep the sprint goal in mind. if the work turns out to be different than they expected, what do they do?

Answer 35

they collaborate with the PO to negotiate the scope of the sprint backlog within the sprint

Question 36

scrum artifact, sprint backlog, commitment - sprint goal: as the developers work during the sprint, they keep the sprint goal in mind. if the work turns out to be different than they expected, they collaborate with the PO to negotiate the scope of the sprint backlog within the sprint. they do this without affecting what?

Answer 36

the sprint goal

Question 37

scrum artifacts, increment: what is this?

Answer 37

a concrete stepping stone towards to the product goal

Question 38

scrum artifacts, increment: each increment is ___ to all ___ increments and thoroughly ___, ensuring what..?

Answer 38

- additive, prior, verified - ensuring that all increments work together

Question 39

scrum artifacts, increment: in order to provide value, the increment must be what?

Answer 39

usable

Question 40

scrum artifacts, increment: how many increments may be created within a sprint

Answer 40

multiple

Question 41

scrum artifacts, increment: when is the sum of the increments presented? thus supporting what?

Answer 41

at the sprint review thus supporting empiricism

Question 42

scrum artifacts, increment: however, an increment may be delivered to stakeholders when?

Answer 42

prior to the end of the sprint

Question 43

scrum artifacts, increment: the sprint review should never be considered as what?

Answer 43

a gate to releasing value

Question 44

scrum artifacts, increment: work cannot be considered part of an increment unless what?

Answer 44

it meets the definition of done

Question 45

scrum artifacts, increment, commitment - definition of done: what is the DoD?

Answer 45

a formal description of the state of the increment when it meets the quality measures required for the product

Question 46

scrum artifacts, increment, commitment - definition of done: at what moment is an increment "born"?

Answer 46

when a product backlog item meets the definition of done

Question 47

scrum artifacts, increment, commitment - definition of done: how des the DoD, create transparency?

Answer 47

by providing everyone a shared understanding of what work was completed as part of the increment

Question 48

scrum artifacts, increment, commitment - definition of done: if a product backlog item does not meet the DoD, what does this mean?

Answer 48

it cannot be released or even presented at the sprint review

Question 49

scrum artifacts, increment, commitment - definition of done: if a product backlog item does not meet the DoD, it cannot be released or even presented at the sprint review. what happens instead?

Answer 49

it returns to the product backlog for future consideration

Question 50

scrum artifacts, increment, commitment - definition of done: when must the DoD for an increment be followed as a minimum?

Answer 50

if the DoD of the increment is part of the standards of the organisation

Question 51

scrum artifacts, increment, commitment - definition of done: if the DoD for an increment is not on organisational standard, what must the scrum team do?

Answer 51

create a definition of done appropriate for the product

Question 52

scrum artifacts, increment, commitment - definition of done: who is required to conform to the definition of done?

Answer 52

the developers

Question 53

scrum artifacts, increment, commitment - definition of done: what happens if there are multiple scrum teams working together on a product?

Answer 53

they must mutually define and comply with the same definition of done