PSM Course Flashcards

1
Q

What are the three pillars of scrum?

A

Transparency, Inspection, Adaptation

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

What are the five values of scrum?

A

Courage, Commitment, Focus, Respect, Openness

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

What is scrum?

A

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

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

What are the primary roles on a scrum team?

A

Developer, Produce Owner, Scrum Master

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

What is the role of a developer on a scrum team?

A

Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.

The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

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; and,

Holding each other accountable as professionals.

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

What is the role of a product owner on the scrum team?

A

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.

The Product Owner is also accountable for effective Product Backlog management.

For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review.

The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.

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

What is the role of a scrum master on a scrum team?

A

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

Scrum Masters are true leaders who serve the Scrum Team and the larger organization.

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

How does the scrum master serve the team?

A

Coaching the team members in self-management and cross-functionality;

Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done;

Causing the removal of impediments to the Scrum Team’s progress; and,

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
9
Q

How does the 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; and,

Facilitating stakeholder collaboration as requested or needed.

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

How does the scrum master serve the organization

A

Leading, training, and coaching the organization in its Scrum adoption;

Planning and advising Scrum implementations within the organization;

Helping employees and stakeholders understand and enact an empirical approach for complex work; and,

Removing barriers between stakeholders and Scrum Teams.

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

What are the 5 scrum events?

A

Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint retrospective

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

What is a sprint?

A

Sprints are the heartbeat of Scrum, where ideas are turned into value.

They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.

All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints.

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

What are some guidelines for during the sprint?

A

No changes are made that would endanger the Sprint Goal;

Quality does not decrease;

The Product Backlog is refined as needed; and,

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

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

What is the maximum length of a sprint and why?

A

Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning cycles and limit risk of cost and effort to a smaller time frame. Each Sprint may be considered a short project.

A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.

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

What are the three topics discussed during sprint planning

A

Topic One: Why is this Sprint valuable?

Topic Two: What can be Done this Sprint?

Topic Three: How will the chosen work get done?

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

What is the daily scrum?

A

The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.

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

What is a sprint review? Why is it important?

A

The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.

During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.

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

What is a sprint retrospective?

A

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.

The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.

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

What are scrum artifacts? Name 3 and what they are for.

A

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.

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

What is a product backlog?

A

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.

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

What is a product goal?

A

Commitment: Product Goal
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.

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

What is a sprint backlog?

A

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).

The Sprint Backlog is a plan by and for the Developers. It 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, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.

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

What is the sprint goal?

A

Commitment: Sprint Goal
The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.

The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. 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 Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.

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

What is an Increment?

A

An Increment is a concrete stepping stone toward the Product Goal (ex: a release or a feature). Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.

Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.

Work cannot be considered part of an Increment unless it meets the Definition of Done.

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

What is a definition of done?

A

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.

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

What is empiricism

A

Empiricism in the philosophy of science emphasizes evidence, especially as discovered in experiments. It is a fundamental part of the scientific method that all hypotheses and theories must be tested against observations of the natural world rather than resting solely on a priori reasoning, intuition, or revelation.

Empiricism, often used by natural scientists, says that “knowledge is based on experience” and that “knowledge is tentative and probabilistic, subject to continued revision and falsification”.[5] Empirical research, including experiments and validated measurement tools, guides the scientific method.

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

What is directly related to QUALITY

A

Definition of Done

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

What are the two things to improve at a retro?

A

Quality + Effectiveness

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

What is the point of scrum

A

To create a done increment

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

A demo to promote the product to stakeholders happens during the Sprint Review, true or false

A

False. A demo can happen but it shouldn’t be to promote the product, just show what has been accomplished

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

Inspect marketplace changes and potential use of the product is part of which sprint event?

A

Sprint Review

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

WHO adapts their plan each day towards the Sprint Goal?

A

The Developers

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

WHO serves the organization, the PO and the scrum team?

A

Scrum Master

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

WHO instills quality by adhering to a DoD

A

Developers

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

WHO coaches team members in self-management and cross-functionality?

A

Scrum Master

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

WHO is accountable for the scrum team’s effectiveness?

A

Scrum Master

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

WHO are true leaders on the team that serve the organization and the Scrum Team?

A

Scrum Master

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

WHO maximizes the value of the Product?

A

PO

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

WHO are required to confirm to the DoD

A

Developers

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

WHO are accountable for creating a valuable, useful Increment every sprint?

A

Developers

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

WHO has a final say on the content and ordering of the Product Backlog?

A

PO

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

WHO is cross-functional and has all the skills required to create value each sprint?

A

Developers

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

WHO typically has 10 or fewer members?

A

The Scrum Team

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

WHO has the authority to cancel the sprint?

A

PO

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

WHO is accountable for establishing scrum as in the scrum guide?

A

Scrum Master

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

WHO develops and explicitly communicates the Product Goal

A

PO

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

WHO are the people in the scrum team committed to creating any aspect of an Increment during the sprint?

A

Developers

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

WHO ensures that the Product Backlog is visible, transparent and understood?

A

PO

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

What has no sub-teams or hierarchies?

A

The Scrum Team

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

WHO is responsible for sizing the work to be done?

A

Developers

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

WHO is self managing, they internally decide what they do, when and how?

A

The Scrum Team

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

WHO creates and clearly communicates Product Backlog items?

A

PO

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

What is a fixed length event of a month or less to create consistency?

A

A sprint

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

Which event improves communication, identifies impediments, promotes quick decision making and eliminates other meetings?

A

Daily Scrum

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

Which event is the second to last of the sprint?

A

Sprint Review

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

What focuses on the Sprint Goal and produces an actionable plan towards the next day of work?

A

Daily Scrum

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

Which event is for the developers of the Scrum Team?

A

Daily Scrum

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

Which event can be cancelled if the Sprint Goal becomes obsolete?

A

The Sprint

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

Which events purpose is to inspect the sprint goal and adjust the sprint backlog as necessary?

A

Daily Scrum

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

What is the first event of the sprint?

A

Sprint Planning

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

What is time-boxed for 8 hours for a one-month sprint?

A

Sprint Planning

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

Which event addresses the topic: How will the chosen work be done?

A

Sprint Planning

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

At which event do the Scrum Team collaborate with stakeholders to discuss what has been done and collaborate on what to do next?

A

Sprint Review

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

What should never be a gate to releasing value?

A

Sprint Review

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

At which event does the team collaborate to define a sprint goal that communicates why the sprint is valuable for the stakeholders?

A

Sprint Planning

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

Which event is a working session and should avoid being limited to a presentation?

A

Sprint Review

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

Which event concludes the sprint?

A

Sprint Retrospective

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

Which event addresses the topic, why is the sprint valuable?

A

Sprint Planning

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

During which event do Developers discuss with the PO and pull items from the product backlog into the sprint backlog?

A

Sprint Planning

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

All the work necessary to complete the Product Goal happens in this event

A

Sprint

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

Each of these can be considered a short project

A

Sprint

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

The scrum team discusses what went well during the sprint, what problems it encountered and how they were (or were not) solved

A

Sprint Retrospective

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

Time-boxed to 4 hours for a one-month sprint

A

Sprint Review

74
Q

Time-boxed to 3 hours for a one-month sprint

A

Sprint Retrospective

75
Q

The purpose of this event is to inspect the outcome of the Sprint and determine future adaptations

A

Sprint Review

76
Q

The purpose of this event is to plan ways to improve effectiveness and quality

A

Sprint Retrospective

77
Q

A new one starts immediately after the conclusion of the previous one

A

Sprint

78
Q

The purpose of this event is to turn ideas into value

A

Sprint

79
Q

This event occurs at the same time and the same place every day

A

Daily Scrum

80
Q

This event is an opportunity for the scrum team to identify the most helpful changes to improve its effectiveness

A

Sprint Retrospective

81
Q

For each selected Product Backlog item the developers plan the work necessary to create an Increment that meets the definition of done.

A

Sprint Planning

82
Q

Time boxed to 15 minutes

A

Daily Scrum

83
Q

Inspect how the last sprint went in regards to individuals, processes, tools and interactions and the definition of done

A

Sprint Retrospective

84
Q

Addresses the topic, what can be done in the sprint

A

Sprint Planning

85
Q

In order to provide value, this must be usable

A

An Increment

86
Q

Updated throughout the Sprint as more is learned

A

Sprint Backlog

87
Q

If the work turns out more than expected, Developers collaborate with the PO to negotiate scope without affecting this

A

Sprint Goal

88
Q

A long term objective for the scrum team

A

Product Goal

89
Q

Is additive to all the prior ones and thoroughly verified, ensuring all of these work together

A

Increment

90
Q

Lives in the Product Backlog

A

Product Goal

91
Q

Must be finalized prior to the end of Sprint Planning

A

Sprint Goal

92
Q

The rest of the Product backlog emerges to define what will fulfill this commitment

A

Product Goal

93
Q

Refinement is an ongoing activity to add details such as description, order, size to items in this artifact

A

Product Backlog

94
Q

Describes a future state of the product which can serve as a target for the Scrum Team to plan against

A

Product Goal

95
Q

If there are multiple scrum teams working on a product they must mutually define and comply with the same version of this

A

Definition of Done

96
Q

Work can not be considered part of this unless it meets the definition of done

A

Increment

97
Q

A plan by and for the developers

A

Sprint Backlog

98
Q

The sum of these are presented at the sprint review thus supporting empiricism

A

Increments

99
Q

Creates transparency by providing a shared understanding of the work completed as part of the increment

A

Definition of Done

100
Q

If a product backlog item does not meet this it can not be released or even presented at the Sprint Review

A

Definition of Done

101
Q

A commitment by the developers it provides flexibility in terms of the exact work needed to achieve it

A

Sprint Goal

102
Q

Is the single objective for the sprint

A

Sprint Goal

103
Q

Refinement is the act of breaking down items of this artifact into smaller and more precise items

A

Product Backlog

104
Q

Concrete stepping stone towards the product goal

A

Increment

105
Q

Creates coherence and focus encouraging the scrum team to work together instead of focus on separate initiatives

A

Sprint Goal

106
Q

Is the single source of work undertaken by the scrum team

A

Product Backlog

107
Q

Created during the sprint planning event and then added to the sprint backlog

A

Sprint Goal

108
Q

If part of the standards of the organization all scrum teams must meet this. If not, the scrum team must create one for the product

A

Definition of Done

109
Q

Multiple of these may be created within a sprint

A

Increments

110
Q

Is composed of the sprint goal, multiple items from the product backlog, and a plan for how to create the increment(s)

A

Sprint Backlog

111
Q

Should have enough detail that developers can inspect their progress in the daily scrum

A

Sprint Backlog

112
Q

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

A

Product backlog

113
Q

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

A

Sprint backlog

114
Q

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

A

Definition of Done

115
Q

The moment a product backlog item meets this an increment is born

A

Definition of done

116
Q

The scrum team must fulfill or abandon this before taking on the next

A

Product Goal

117
Q

What are the scrum values?

A

Courage, Focus, Commitment, Respect, Openness

118
Q

Is there a methodology for the scrum master to follow?

A

There is no methodology for the scrum master to follow but there is a set of intervention choices and behavioural stances from which to choose depending on the context

119
Q

What are the (8) scrum master choices?

A

Teacher, mentor, point north, actively do nothing, uphold scrum, take action, facilitator, coach

120
Q

What is a leaders job in a chaotic environment?

A

take action to re-establish order, prioritize and select actionable work, look for what works rather than perfection, act sense and respond

121
Q

What is a leader’s job in a complex environment

A

Create bounded environments for action, increase levels of interaction and communication, servant leadership, generate ideas, probe sense and respond

122
Q

What is a leader’s job in a complicated environment

A

Utilize experts to gain insights, user metrics to gain control, sense, analyze and respond, command and control

123
Q

What is a leader’s job in a simple environment?

A

Use best practices, extensive communication not necessary, establish patterns and optimize to them, command and control

124
Q

What are some characteristics of scrum master’s leadership?

A

success measured by the growth of others, influence individuals and teams to take greater responsibility for actions and outcomes, lead without using authority or force, inspire others to higher greatness, leverage scrum values to promote a psychologically safe environment

125
Q

In what ways can we compare waterfall to scrum to show its benefits?

A

Visibility, Ability to Change, Business Value, Risk

126
Q

What are the three legs of empiricism?

A

Transparency, Inspection, Adaptation

127
Q

What requires trust and courage?

A

Transparency

128
Q

What are the scrum artifacts?

A

Product Backlog, Sprint Backlog, Incremeent

129
Q

What are the scrum commitments?

A

Product Goal, Sprint Goal, DoD

130
Q

Who manages the sprint backlog?

A

Developers

131
Q

Who creates increments every sprint and is self managing and cross functional?

A

The scrum team

132
Q

How does scrum provide flexibility?

A

Every sprint the stakeholders (by way of the PO) can have the team do something new as they see fit

133
Q

How does scrum provide stability?

A

The stakeholders leave the team alone to work on what they need most

134
Q

Describe the sprint planning flow

A

Why - define the sprint goal
What - analyze, evaluate and select backlog items for the sprint
How - decompose enough work into an actionable plan

135
Q

Describe the flow of the sprint review

A

Review Sprint
Increment and Sprint Outcomes
Current Business conditions
PBacklog and progress towards product goal

136
Q

What is the inspection part of sprint planning?

A

Product backlog, product goal, DoD

137
Q

What is the inspection part of the daily scrum?

A

progress toward the sprint goal

138
Q

What is the inspection part of the sprint review?

A

Increment, sprint, PBacklog, Progress towards product goal

139
Q

What is the inspection part of the retro?

A

Inspect the sprint, DoD. Look at quality and effectiveness

140
Q

What is the adaptation part of sprint planning?

A

Sprint backlog, sprint goal

141
Q

What is the adaptation part of the daily scrum?

A

Spring backlog

142
Q

What is the adaptation part of the sprint review?

A

Product backlog

143
Q

What is the adaptation part of the sprint retro?

A

Actionable improvements, DoD

144
Q

What is the relationship between Tech debt and actual work required?

A

Undone work and technical debt increase the actual work (by creating rework)

145
Q

What is the relationship between tech debt and value?

A

As technical debt builds up, the ability to create value drops.

146
Q

What are some actions that can be taken to reduce technical debt

A

Create transparency about the technical debt in the product backlog, improve the DoD to lower the chance for TD in the future, Stop creating new TD and start paying back the existing one a bit at a time

147
Q

What are some product qualities that serve the DoD?

A

Quality code base, valuable functionality only, architectural conventions, according to design or style guide, according to usability standards, documented, service levels guaranteed

148
Q

What are some development standards that serve the DoD?

A

Pair programming, TDD, ATDD, BDD, refactoring, UI testing, functional testing, performance testing, CICD

149
Q

Describe a PRODUCT mindset vs a PROJECT mindset

A

Product - continuously driven by business metrics outside in (user adoption / retention, revenue, cost savings). Leads to less waste, more creativity and more releases
Project - success upfront defined inside out (scope, time, budget). Leads to less business involvement and more task management

150
Q

Choose the best answer. The length of a sprint should be:
A - Short enough to keep business risk acceptable to the PO
B - Short enough to synchronize dev work with other business events
C - One month or less
D - All of the above

A

D - all of the above.
All of these choices are appropriate considerations for determining the length of a sprint

151
Q

What are some techniques for PB ordering and value?

A

Allocate pts from a fixed total, planning poker, buy a feature…

152
Q

What are some methods of PB Organization?

A

Priority, Development Cohesion, Business Cohesion, Implementation Cohesion, Intentions

~ Cohesion simplifies development and implementation

153
Q

Describe the difference between Absolute estimation, relative estimation and flow metrics

A

Absolute - traditional (time or effort based). Ex: gantt charts
Relative estimation - easy to get started with and allows for uncertainty. Ex: Tshirt sizing
Flow metrics - easiest to use, data drive, value focused (velocity, efficiency, time, load)

154
Q

What are some agile solutions for fixed price, fixed date work?

A

Add contract provisions - any requirement that hasn’t already been worked on can be swapped out for another of equal size, order of the requirements can be changed, customer may request additional releases at any time prevailing time and material fees, customer may terminate contract early

155
Q

True or false, scrum teams must be co-located

A

False

156
Q

True or false, two people cannot form a scrum team

A

false

157
Q

true or false, scrum teams cannot be bigger than 10 members

A

false

158
Q

True or false, a developer cannot be a product owner or a scrum m aster

A

false

159
Q

True or false, every developer must be able to perform every type of task

A

False

160
Q

True or false, if scrum teams consult external people, they are not self-managing

A

false

161
Q

True or false, all members of the scrum team need to be present on the team full-time

A

false

162
Q

True or false, developers must have clear sub-roles (coder, tester, analyst, writer)

A

false

163
Q

What are the three main motivators of people?

A

Autonomy, Mastery, Purpose

164
Q

How does vertical slicing enhance transparency?

A

Each team has all the skills to turn PB into releasable increments, work is divided by end-user functionality, work is integrated continuously, transparency is ensured – no unknown or undone work

165
Q

What happens when people have to work consistently more?

A

People work at a sustainable pace, if developers have to consistently work more, quality and creativity drop

166
Q

What are the assets of a collaborative team?

A

Trust, conflict, commitment, accountability, goals

167
Q

How does a scrum master serve the team?

A

Lead by example, create a safe environment, facilitate consensus, learn to read the room, show patience, restrain from solving, be comfortable with failure, care for people, show low tolerance for organizational impediments

168
Q

Describe predictive management vs empirical management

A

Predictive - long term detailed plans, assign and control the work, maximize capacity and effort
Empirical - goals, vision, direction. Foster the environment and remove impediments. Share incremental feedback. Manage for value

169
Q

What kind of commitments are taken the most seriously?

A

Teams take commitments they make more seriously than commitments others make for them. When a team commits to a sprint themselves they are more dedicated than if someone else determines and assigns the work for them

170
Q

What is the most productive kind of person?

A

Teams are more productive than the same number of individuals, teams and people do their best work when not interrupted

171
Q

How does a scrum master measure their own success?

A

By the growth and success of others. they inspire, enable, and challenge others to higher greatness

172
Q

What are the scrum master responsibilities?

A

Ensures scrum is understood and enacted, facilitates scrum events, helps everyone adhere to scrum theory practices and rules, helps people embrace and live scrum values, true leader for the scrum team, causes change that improves quality or productivity, embody agility to the organization

173
Q

Move away from coordinating individuals and individual contributions

A

Move toward coaching people in scrum and positive team behaviours by embodying scrum values

174
Q

Move away from providing answers as a subject matter expert

A

Move toward self-management within scrum teams

175
Q

Move away from investing in specific outcomes (budget and scopr)

A

Move toward helping PO’s manage product backlogs and work with stakeholders

176
Q

Move away from deadlines

A

Move towards focusing POs on flow and value

177
Q

Move away from prescribing technical solutions

A

Move towards helping developers effectively use and improve the DoD

178
Q

Move away from fixing problems

A

Move towards guiding scrum teams to discover what works best for them

179
Q

What are some of the impediments a scrum master removes?

A

Organizational processes, adjacent processes, development excellence, scrum team forming, understanding scrum

180
Q

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?

A

Developers