PSM1 Flashcards

1
Q

Scrum Definition

A
  • lightweight framework
  • helps generate value
  • adaptive solutions for complex problems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Meaning of empiricism

A

knowledge comes from experience

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

Meaning of lean thinking

A

reduces waste and focuses on the essentials

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

How does Scrum control risk and optimise predictability?

A

It employs an iterative, incremental approach

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

What are the 3 Scrum pillars?

A
  1. Transparency
  2. Inspection
  3. Adaptation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the 5 Scrum Values?

A
  1. Commitment
  2. Focus
  3. Openness
  4. Respect
  5. Courage

FORCC

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

Who are involved in a Scrum Team?

A

1 Scrum Master, 1 Product Owner, Developers

Focus on 1 objective - Product Goal

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

Meaning of Cross-functional

A

Meaning the members have all the skills necessary to create value each Sprint

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

Meaning of Self-managing

A

Meaning they internally decide who does what, when and how

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

How many people in a Scrum Team?

A

10 or fewer people

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

What should we do if the Scrum Teams become too large?

A

consider reorganising into multiple Scrum Teams, but still focus on the SAME product, SAME Product Goal, Product Backlog, and Product Owner, SAME Definition of Done

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

Meaning of “Sustainable pace”

A

If the Development Team is delivering more features but, for example, is working overtime, this is not a sustainable pace.

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

Who is accountable for creating Increment every Sprint?

A

Entire Scrum Team

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

List out the Developers’ accountability

A
  • Creating a plan for the Sprint, the Sprint Backlog
  • Instilling quality by adhering to a Definition of Done
  • Adapting their plan each day toward the Sprint Goal
  • Holding each other accountable as professionals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

List out the Product Owner’s accountability

A
  • Maximise the value of the Product
  • Effective Product Backlog management
  • Developing and explicitly communicating the Product Goal
  • Creating and communicating Product Backlog Items
  • Ordering Product Backlog Items
  • Ensuring that the Product Backlog is transparent, visible and understood
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Can Product Owner delegate the responsibility to others?

A

Yes, Product Owner can delegate the responsibility to others but remains accountable.

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

Can stakeholders change the Product Backlog directly?

A

No, only Product Owner (1 person) can change the Product Backlog and represents the needs of stakeholders.

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

List out the Scrum Master’s accountability

A
- Establish Scrum:
Help everyone (Scrum Team + Organisation) to understand Scrum theory
  • Scrum Team’s effectiveness
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

How does Scrum Master serve the Scrum Team?

A
  • Coaching the team members in self-management and cross-functionality
  • Helping the Scrum Team focus on creating high-value Increments that meet Definition of Done
  • Causing the removal of impediments to the Scrum Team’s progress
  • Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

How does Scrum Master serve the Product Owner?

A
  • Helping find techniques for effective Product Goal definition and Product Backlog management
  • Helping the Scrum Team understand the need for clear and concise Product Backlog Items
  • Helping establish empirical product planning for a complex environment
  • Facilitating stakeholders collaboration as requested or needed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

How does Scrum Master serve the Organisation?

A
  • Leading, training and coaching the organisation in its Scrum adoption
  • Planning and advising Scrum implementations within the organisation
  • Helping employees and stakeholders understand and enact an empirical approach for complex work
  • Removing barriers between stakeholders and Scrum Teams
22
Q

Why do we need Scrum Events?

A
  • opportunity to inspect and adapt Scrum artifacts

- enable the transparency

23
Q

How long should 1 Sprint last?

A

One month or less

24
Q

What events does One Sprint consist of?

What are the 4 formal events for inspection and adaptation?

A

1) Sprint Planning
2) Daily Scrums
3) Sprint Review
4) Sprint Retrospective

25
Q

Can we make changes during the Sprint?

A

Yes, as long as it wouldn’t endanger the Sprint Goal.

Product Backlog is refined as needed.
Scope may be clarified and renegotiated with the Product Owner as more is learned.

26
Q

Could the Sprint be cancelled?

A

Yes, the Sprint could be cancelled if the Sprint Goal becomes obsolete.

27
Q

Who can cancel the Sprint?

A

Only the Product Owner has the authority to cancel the Sprint.

28
Q

Who create Sprint Plan during Sprint Planning event?

A

Entire Scrum Team

29
Q

Which 3 topics does Sprint Planning address?

A
  1. Why is this Sprint valuable?
  2. What can be Done this Sprint?
  3. How will the chosen work get done?
30
Q

Who can select items from Product Backlog to include in the current sprint?

A

Developers

31
Q

When are the items selected from Product Backlog?

A

During Sprint Planning event

32
Q

The Sprint Backlog is composed of….(3 things)

A
  1. (WHY) Sprint Goal
  2. (WHAT) Product Backlog Items
  3. (HOW) Plan
33
Q

What is the timebox for Sprint Planning event?

A

Maximum of 8 hours for a one-month Sprint

34
Q

How long should Daily Scrum last?

A

15-minute event

35
Q

Who can join the Daily Scrum?

A

Developers

36
Q

2 Main purposes of Daily Scrum

A
  1. Focuses on progress toward the Sprint Goal

2. Produces an actionable plan for the next day of work

37
Q

2 purposes of Sprint Review event

A
  1. Inspect the outcome of the Sprint (what was accomplished in the Sprint)
  2. Determine future adaptations (what to do next)

Product Backlog may be adjusted

38
Q

How long should Sprint Review last?

A

Maximum of 4 hours for a one-month Sprint

39
Q

1 purpose of Sprint Retrospective

A
  • Plan ways to increase quality and effectiveness

inspects how the last Sprint went
Discuss what went well during the Sprint
What problems it encountered
How those problems were (were not) solved

40
Q

How long should Sprint Retrospective last?

A

Maximum of 3 hours for a one-month Sprint

41
Q

What are 3 Scrum Artifacts?

A
  1. Product Backlog
  2. Sprint Backlog
  3. Increment
42
Q

What is Product Backlog?

A

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

Define “what” will fulfil the Product Goal

43
Q

What is Product Backlog Refinement?

A

The act of breaking down and further defining Product Backlog items into smaller more precise items

44
Q

What is the commitment of Product Backlog?

A

Product Goal.

Product Goal is in the Product Backlog.

45
Q

What is the commitment of Sprint Backlog?

A

Sprint Goal.

Single objective for the Sprint.
Created during Sprint Planning event.
Sprint Goal is in Sprint Backlog

46
Q

What will Developers do if the work turns out to be different than they expected?

A

Collaborate with Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.

47
Q

What is an Increment?

A

A concrete stepping stone toward the Product Goal

Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all increments work together.

Increment must be usable in order to provide value.

Increment =/= releasable

48
Q

What happen if there are multiple Increments within a Sprint?

A

Sum of Increments is presented at the Sprint Review.

But One Increment may be delivered to stakeholders prior to the end of the Sprint.

49
Q

What is the commitment of Increment?

A

Definition of Done.

Product Backlog item meets Definition of Done = Increment

50
Q

What is Definition of Done?

A

A formal description of the state of the Increment when it meets the quality measures

51
Q

What to do if a Product Backlog Item in Sprint Backlog doesn’t meet the Definition of Done?

A

Cannot be released/ presented at the Sprint Review

Returns to the Product Backlog