Brainscape's Knowledge GenomeTM

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


See full index

Udemy - Scrum Master Certificate > Artifacts > Flashcards

Artifacts Flashcards

1
Q

What are the Comittments to each of the 3 Artifacts:

  • Product Backlog
  • Sprint Backlog
  • Increment
A

Product Backlog => Product Goal

Sprint Backlog => Sprint Goal

Increment => Definition of Done

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

What is the Product Goal?

And where is it contained?

A
  • describes a future state of the product which can serve as a target for the Scrum Team to plan against.
  • stepping stones towards the Product Vision

Contained:
=> in the Product Backlog.

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

Could you have multiple Product Goals?

A

=> yes

but Scrum Team must focus on one Product Goal at a time

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

Who is responsible for developing and explicitly communicating the Product Goal?

A

=> the Product Owner

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

Can the Product goal be the Product itself?

A

No

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

What is the Product Backlog?

And name 2 Characteristics of it.

A

=> an ordered list of the work to be done in order to create, maintain and sustain a product. (pflegen & aufrechterhalten)

=> it is dynamic and emergent

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

Who manages the Product Backlog?

A

the Product Owner

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

Can there be more Product Backlogs per Product?

A

No

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

All the Product Backlog items are detailed.

True or False.

A

=> False

The Product Backlog follows „Just-in-time“ requirements

=> Only top Product Backlog items are detailed, the ones ready for the upcoming Sprint
(„ready“ => when it can be done in 1 Sprint)

not wasting time with the remaining ones

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

What do the Product Backlog items contain?

A

a description which might be using notations as EPICS and USER STORIES

(Eine Beschreibung, die als Epics oder User Stories notiert werden kann)

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

Why do we have just-in-time requirements?

A

because we expect things to change

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

What are Epics?

A

=> large Product Backlog items
(too large to fit a Sprint)

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

What are User Stories
(or bug descriptions)?

A

=> small refined items

that can be delivered whithin a Sprint

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

Name the 3 compenents of User Strories.

A

Card
* written description (from the perspective of a customer or user) of the functionality that will be valuable to them
* Usually they are written on paper cards

Conversation
* represents the collaboration between the PO and the developers (business & technical people)

Confirmation
* List of criteria, the Scrum Team will define to serve as a verification if the product delivered suits the needs

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

How is the Product Backlog ordered?

A

=> Scrum guide does not give details about how the Product Backlog should be ordered

=> therefore it can be ordered using whatever factors or techniques that the PO judges as appropriate

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

Name 4 widely used techniques/factors to order the Product Backlog.

A
  • Size
  • Risk
  • Value
  • Dependencies
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Who is responsible for sizing the Product Backlog (Ordnen nach Größe)?

A

=> The Developers
since they are the ones who will transform the Product Backlog Item into part of a Definition of Done Increment

=> The PO may influence the Developers by helping them understand and select trade-offs, but only Developers estimate the Product Backlog Items

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

What is one of the most popular measure units to size the Product Backlog items in Agile?

And which Scale do you use?

A

=> Story point

(agile alternative to hours and days)

In Story they use a very particular scale: Semi-Fibonacci scale
1, 2, 3, 5, 8, 13, 20, 40, 100

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

What is Planning Poker?

A

=> Most used estimation technique to size Poduct Backlog Items

  • each Developer has an deck of cards with the Semi-Fibonacci numbers
  • the “rank” each Product Backlog item with their cards
  • If everyone has the same estimate => perfect!
  • if not they do another round, until consensus is reached
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is the Kano Model?

A

=> one technique to define the value for Product Backlog items

by classifying it into 1 of 3 categories:
* Mandatory
* Linear
* Exiter

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

What is the Product Backlog Refinemet?

A

=> Verfeinerung

  • is the act of breaking down and further defining Product Backlog items into smaller more precise items (adding details, e.g. description order, size, …)
  • to get them ready in the Timebox of one Scrum
22
Q

Who does the refinement of the Product Backlog item?

A

The Scrum Team

23
Q

What is the Definiton of “Ready”?

A

=> a set of criteria that defines when a Product Backlog Item is ready to be executed

24
Q

Name the 3 default criteria of the Definition of “Ready”.

A

Usually we have at least these criteria (default):

  • Acceptance criteria defined
  • Team understands what has to be done
  • Fit a sprint
25
Q

Is the Definition of “Ready” a checklist?

A

=> No,
it is not a checklist or contract!!

=> it is more about a helpful guide for the product backlog refinement that may not always be achievable

=> Because it might becomes a gate that gets into the way of the Scrum Team, instead of supporting it

26
Q

Is it okay for the Scrum team to attempt working on a Product Backlog item that is not 100% ready?

A

Yes

27
Q

Name 3 practices for a Monitoring Progress towards goals.

A
  • The Burn-Down Chart
  • The Burn-Up Chart
  • The Cumulative Flow Chart
28
Q

What is the Burn-Down chart?

A

a chart which shows the amount of work which is thought to remain in a backlog

BUT
the amount of work (Story Points) can increase, what’s not visible in this chart

29
Q

What is the Burn-Up chart?

A

a chart which shows the amount of work which has been completed

=> shows the work done by the team and also the amount of work to be done on the Product Backlog (scope Variation)

30
Q

What is the Cumulative Flow chart?

A

a chart that shows the distribution of all Product Backlog items across various states over time

31
Q

What is the Definition of Done?

A

=> defines what is needed for work to be considered done,

promoting transparency and visibility

32
Q

What happens when a Product Backlog item meets the Definition of Done?

A

an Increment is born

33
Q

What happens if a Product Backlog item does not meet the Definition of Done?

A
  • can not be released
  • can not presented at the Sprint Review
  • returns to the Product Backlog for future consideration
34
Q

What is the difference between the Definition of Done and the Acceptance Critera for User Stories?

A

The Acceptance Criteria are specific for one single user story

The Definition of Done englobes all of them.

35
Q

Who defines the Definition of Done?

A

=> the organization
all Scrum Teams must follow it as a minimum

If the organization doesn’t have one, the Scrum Team must define an appropriate one for the product.

36
Q

When is the Definition of Done defined?

A

=> is a continuous effort

because DoD might evolve,
(Adding, removing or editing the existing criteria whenever the organization or Scrum team feels like it is necessary)

=> might be a topic of discussion for Sprint retrospective meetings

37
Q

If there are multiple Scrum Teams working together on a product, do they mutually define and comply with the same Definition of Done?

A

=> yes, they must!

38
Q

When is an Increment developed?

A

during Sprints

39
Q

When is an Increment born?

A

=> the moment a Product Backlog item meets the Definition of Done

40
Q

Do Scrum Teams need to release the Increment at the end of each Sprint?

A

=> No

=> The Scrum team can release it whenever it feels like it is valuable

=> the Increment must be usable

41
Q

Does the Scrum Team need to wait until the end of a Sprint, to release a version of the Increment?

A

=> No

=> The Scrum team can release it whenever it feels like it is valuable

=> the Sprint Review should never be considered a gate to releasing value

42
Q

What is an Increment?

A

a usable Product,

something concrete users or stakeholders can use / have an authentic experience with to give quality feedback

43
Q

Can multiple Increments be delivered in each Sprint?

A

yes

44
Q

What is the Sprint Backlog?

A

=> is a real-time picture of the work that the Developers plan to accomplish during the Sprint, in order to achieve the Sprint Goal

=> is a plan by and for Developers

45
Q

What is the Sprint Backlog composed (zusammengestellt) of?

A
  • the Sprint Goal (WHY)
  • the selected Product Backlog Items (WHAT)
  • the plan for delivering the Increment (HOW)
46
Q

What is fixed and what is flexible in the Sprint Backlog?

A

Sprint Goal
is defined during the Sprint Planning and remains the same throughout the Sprint

selectec PBIs & Plan
can change

As more is learned it is possible to change the work to be done (update the Sprint Backlog) during a Sprint, without affecting the Sprint Goal.

It should have enough detail that they can inspect their progress in the Daily Scrum.

47
Q

What happens if the Developers need to change the Sprint Backlog?

A

=> If the work turns out different than Developers expected, they collaborate with the PO to negotiate the scope of the Sprint Backlog within the Sprint, without affecting the Sprint Goal.

48
Q

What if someone else wants to change the Sprint Backlog?

A

=> The Sprint Backlog is by and for the Developers. No one can force them to change it.

If someone wants to change it, they need to talk to the PO, which will then have to negotiate with the Developers.

49
Q

When is the Sprint Goal created?

A

during the Sprint Planning event

50
Q

What are the Developers committed to?

A

The Developers commit to the Sprint Goal.
The Sprint Backlog is a forecast.

51
Q

What is a technical dept?

A

the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value earlier.

Udemy - Scrum Master Certificate (7 decks)

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