Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

SAFe Training Cert DONE > Scrum Master > Flashcards

Scrum Master Flashcards

1
Q

What is the 4 elements of the Agile Manifesto?

A

Individuals over processes
software over documentation
collaboration over contracts
responding over planning

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

According to Agile what is the highest priority?

A

Satisfy the customer through early and continuous delivery of valuable software.

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

According to Agile what is the primary measure of progress?

A

working software

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

What are the three pillars of Scrum?

A
  1. transparency
  2. inspection
  3. adaptation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the 5 Scrum values?

A
  1. Courage
  2. Commitment
  3. Focus
  4. Respectd
  5. Openness
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the benefit of the 3 pillars of Scrum?

A

short learning cycles

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

What is an Iteration?

A

single development cycle that includes definition, building, integration and testing of a set of stories from the backlog.

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

What is the SAFe recommended length for an iteration?

A

2 weeks

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

What is the goal of an interation?

A

deliver working software

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

What should you avoid once an interation has begun?

A

adding scope

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

Who own and prioritizes the backlog?

A

The product owner

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

What sort of stories are in the backlog?

A

User and Enabler stories

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

What does implementing stories in vertical slices provide?

A
  1. shorter feedback cycle
  2. Refinement of understanding
  3. more frequent integrations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the 10 SAFe Lean-Agile Prinicples

A
  1. economic view
  2. systems thinking
  3. assume variability
    4.build incrementally
  4. objective are working systems
  5. limit WIP
  6. apply cadence
  7. unlock motivation
  8. decentralize decisions
  9. organize around value
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the two specialty roles on an Agile team?

A
  1. Scrum Master
  2. Product Owner
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the size of an Agile Team?

A

5 to 11 members

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

What are the 4 responsibilities of an Agile Team

A
  1. Create stories
  2. Build stories
  3. Build quality
  4. Commit to PI Objective and Iteration Goals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What are the 4 basic responsibilities of a Scrum Master?

A
  1. Coaches team
  2. Focus on value creation
  3. Removes impediments
  4. Team is timeboxed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is an Agile Release Train?

A

A team of teams synchronized on PIs aligned via Program Backlog

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

What is the size of an ART?

A

5 -12 teams, 50-125+ people

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

What are the 4 ART events?

A
  1. PI Planning
  2. ART Sync
  3. System Demo
  4. Inspect and Adapt
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

How does a Scrum Master support an Agile team?

A
  1. Facilitates events
  2. Servant leader
  3. Builds high-performing teams
  4. Help team improve process
  5. Removes impediments
  6. Foster Agile adoption
  7. Support product owner
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

How does a SAFe Scrum Master support the enterprise?

A
  1. Works with RTE to meet PI Objectives
  2. Coordinates with Scrum Master at PI Planning
  3. Works with the team through iterations and PI
  4. Participates in SOS
  5. Normalizes story estimating
  6. Helps with architecture governance, system integration, system demos
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

What are the 4 stages of high-performing teams?

A
  1. Forming
  2. Storming
  3. Norming
  4. Performing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What are the 5 events in an iteration?

A
  1. Refinement
  2. IP
  3. Daily Standup
  4. Iteration Review
  5. Iteration Retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

What are 5 way meeting can suck?

A
  1. Unclear purpose
  2. No actionable outcomes
  3. Unproductive conflict
  4. boring
    5.off topic discussions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

How often should ART teams integrate?

A

Multiple times per iteration

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

How should Agile teams manage dependencies on other ART teams?

A

Through the System Architect

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

What is the Scrum of Scrums

A

A meeting for scrum masters and RTEs to gain visibility in ART progress and impediments

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

How often are SOS held?

A

weekly

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

What is the most efficient type of team communication?

A

Face to Face

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

When to teams perform best?

A

When the have planned periods of uninterrupted work.

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

What can impact team productivity?

A

A change in team composition.

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

What is a strong team movitivator?

A

Peer pressure

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

How can a team produce more robust products?

A

By having all the cross-functional skills needed

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

What are the 5 dysfunctions of a team?

A
  1. No Trust
  2. Conflict fear
  3. No Commitment
  4. Avoid Accountability
  5. No results.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

What is the key problem for dysfunctional teams?

A

Absence of trust.

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

What is a team’s ultimate competitive advantage?

A

Teamwork.

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

How does SAFe address No results?

A

Results are review at the end of every iteration and release.

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

How does SAFe address avoidance of accountability?

A

Stakeholders, peer pressure, and reviews

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

How does SAFe address Lack of commitment?

A

Teams make shared commitments

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

How does SAFe address fear of conflict?

A

Scrum creates a safe environment for conflict.

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

How does SAFe address absence of trust?

A

The environment is safe.

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

What is the main principle for a leader dealing with conflicts?

A

Spend more time helping things go right than dealing with things that are going wrong

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

What six things can a leader do to avoid conflicts?

A
  1. Humanize team
  2. Common vision/goals
  3. Deal with long term tension
  4. Achieve Concensus
  5. Relentless collaboration
  6. conflict resolution techniques
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

What are the 6 ways to resolve a conflict?

A
  1. Meet with parties
  2. Identify wants
  3. Identify whys
  4. Common goal agreement
  5. Review assumptions
  6. Challenge assumptions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

What is the chief tool to facilitate conflicts?

A

working agreements

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

What are the 5 ways to achieve consensus

A
  1. Why consensus is important
  2. Exchange thoughts
  3. Decompose the disagreement
  4. Ask for proposals
  5. Exchange thoughts
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

What is a PI, Program Increments?

A

A cadence-based event that serves as the heartbeat of th ART that aligns team to a shared mission

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

How often are PIs?

A

Every 8-12 weeks, 10 weeks typical

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

At a PI who owns the Feature Priorities?

A

Product Manager

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

At a PI who owns the story planning and high-level estimates?

A

Development teams

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

What are the 6 benefits of PI Planning?

A
  1. Establishes all-team communication
  2. Aligns development to business goals
  3. Identifies cross-ART dependencies
  4. Provides just the right about of architecture and Lean UX guidance
  5. Matches demand to capacity, eliminates WIP
  6. Fast decision making
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

What is the input for a PI planning process?

A

Prioritized (ala the vision) list of features from a program backlog

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

What is the output for a PI planning process?

A

PI objectives and Program board

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

What is a PI feature

A

A business need that fills a business objective that fits in one PI (e.g 10 weeks)

57
Q

How are PI featues implemented?

A

A set of smaller stories that each fit within development interations that occur during the PI

58
Q

What are the two parts to a PI feature?

A

The description and the benefit hypothesis

59
Q

What is a user story

A

Short description of a small desired functionality, written in the users language

60
Q

What are the three parts of a user story?

A
  1. As a (user role),
  2. I want to (activity)
  3. so that (business value)
61
Q

For User stories what are personas

A

Detailed fictional characters acting as representative user

62
Q

What is the INVEST technique to good user story writing?

A

Independent
Negotiable
Valuable
Esitmable
Small
Testable

63
Q

What are the 3c to composing good user stories?

A

Card
Conversation
Confirmation

64
Q

What are user stories acceptance criteria?

A

It is the user story from a testing point of view.

65
Q

Who creates a user story’s acceptance criteria?

A

The agile team

66
Q

What is the format for acceptance criteria for a user story?

A

Given-When-Then format

67
Q

What are Enabler stories?

A

Stories the build the groundwork for future user stories

68
Q

What are the 4 categories of Enabler stories

A
  1. Infrastructure
  2. Architecture
  3. Exploration
  4. Compliance
69
Q

What are thre types of enabler stories?

A
  1. Technical Spikes
  2. Functional Spikes
  3. Refactors
70
Q

What is a spike enabler story?

A

Research activities

71
Q

Why are spike enabler stories useful?

A
  1. Reduce risk
  2. Improve understanding
  3. Improve estimate reliablity
  4. Imrove required skills
72
Q

How are stories estimated

A

I singular, relative number called a story point

73
Q

What 4 things comprise a story point?

A
  1. Volumen
  2. Complexity
  3. Knowledge
  4. Uncertainty
74
Q

How are story points related

A

They are linearly related, 4 twice as long a 2, 8 for times as long as 2

75
Q

What are the 4 steps of Estimating poker?

A
  1. Distribute decks of cards
  2. Read job
  3. Card selection
  4. Card turnover
  5. Discuss high/low
  6. goto 3 until concensus
76
Q

Who does story point estimating?

A

The entire team

77
Q

Why is it important to estimate with the entire team?

A
  1. Increases accuracy
  2. Builds understanding
  3. Shared commitment
78
Q

What are 3 scrum master anti-patterns with story point estimation

A
  1. Pressure stakeholders
  2. Not everyone participates
  3. Not using adjusted Fibonacci scale
79
Q

What are 3 scrum master anti-patterns with story point estimation

A
  1. Pressure stakeholders
  2. Not everyone participates
  3. Not using the adjusted Fibonacci scale
80
Q

What are 5 scrum master best practices with story point estimation?

A
  1. Encourage everyone
  2. Ensure relative numbers used
  3. Focus on contested items
  4. Identify SME to participate
  5. Keep time spent to a minimum
81
Q

What are 7 agenda items on day 1 PI planning meeting?

A
  1. Business context
  2. Product Vision
  3. Architecture Vision
  4. Planning context
  5. Team breakouts
  6. Draft Plan review
  7. Management review/problem solving
82
Q

What happens during team breakouts in PI Planning?

A

Teams develop draft plans and
Identifies risks

83
Q

What are the 7 agenda items on day 2 PI planning meeting?

A
  1. Planning adjustments
  2. Team Breakouts
  3. Final plan review
  4. Program risks
  5. Confidence vote
  6. Plan rework
    7 Planning Retrospective
84
Q

What is a PI Objective?

A

Business summaries of what each team intends to deliver this PI

85
Q

Do PI Objectives always directly relate to Features in the backlog?

A

Not always, but usually

86
Q

What are the two types of Featuers

A
  1. Enabler Feature
  2. Business Features
87
Q

What are uncommitted objectives?

A

PI objectives that cannot be committed to for the current PI

88
Q

What is the benefit of uncommitted objectives?

A

Help improve the predictability of delivering business value

89
Q

What are uncommitted objectives used for?

A

Calculating load

90
Q

What is the scrum master’s role in the first team breakout meeing during PI planning?

A
  1. Ensure team has draft plan
  2. Identify as many risks and dependencies
  3. Secure SME
  4. Facilitate team coordination
91
Q

What are 4 scrum master anti-patterns for PI planning team breakouts?

A
  1. Incomplete plan at end of breakout timebox
  2. Too much time analyzing stories
  3. Not available enough to every team (shared scrum masters)
  4. Not having enough time to plan as part of team (shared scrum masters)
92
Q

What happens at the management review and problem solving meeting during PI planning?

A

management makes adjustments to scope and objectives

93
Q

What type of Enabler does a System architect review during a system demo?

A

Enabler Features

94
Q

What are the two primary aspect of Lean-Agile Mindset?

A
  1. Lean thinking
  2. Embracing agility
95
Q

How does a scrum master help the team improve toward technical excellence?

A

Focus on built in quality

96
Q

Who owns the daily standup

A

Scrum master

97
Q

What three things does a PI program board contain?

A
  1. Feature delivery dates
  2. Milestones
  3. Dependencies
98
Q

In SAFE who owns the decision for releasing changes into production?

A

Solutions owner

99
Q

What are the two critical constructs to delivering continious value?

A
  1. Cadence
  2. synchronization
100
Q

What is reason why some teams never reach stage 4

A

No one guides them

101
Q

Which demo is performed in the IP iteration?

A

demo of all ART interations

102
Q

What is the goal of PI planning team breakout #2

A

Create final plans

103
Q

What does the business owner do during team breakout #2?

A

Assigns busienss values to PI objectives

104
Q

What is the numbering system for business value assignments in PI Planning?

105
Q

What 4 things happen during the final plan review during PI planning?

A
  1. Changes to capacity and load
  2. Business Values scores on PI Objectives
  3. Program risk and impediments
  4. QA session
106
Q

In PI planning who reviews the final plan?

107
Q

In PI Planning who asks for plan acceptance?

A

Business ownde

108
Q

What is the ROAM technique to address remaing PI planning risks?

A

Resolved
Owned
Accepted
Mitigated

109
Q

What are the two parts of the ART committment?

A
  1. Agree to to meet objectives
  2. Escalate immediately
110
Q

What are the scrum master best practices for PI Planning

A
  1. Maintain the timebox
  2. Ensure team builds a plan they can commit to
  3. Ensure that the team is honest in the vote
  4. facilitate coordination
  5. Be a request buffer
  6. Manage the program board
  7. facilitate the retrospective
111
Q

What are 4 scrum master anti-patterns for PI planning

A
  1. Pressure team to overcommit
  2. Team commits due to failure
  3. Over planning ahead of time
  4. plan rather than alignment becomes goal
112
Q

what is the iteration planning flow

A
  1. establish capacity
  2. esitmating
  3. detailing
  4. goals
  5. committing to goals
113
Q

what are the 4 steps to establishing capacity for IP planning?

A
  1. Apply capacity allocation
  2. Quanitfies capacity
  3. Determine team availablility
  4. PO and teams select highest priority from backlog
114
Q

What does capacity allocation help with?

A
  1. Alleviate tech debt velocity degradation
  2. Keeps customers happy with bug fixes
115
Q

When does capacity allocation change?

A

At iteration or PI boundaries

116
Q

What are the 3 steps to story analysis in IP planning?

A
  1. PO presents stories in priority order
  2. Discuss and anlyze each story
  3. repeat 2 until capacity is reached.
117
Q

What do iteration goals provide?

A
  1. Clarity
  2. Commitment
  3. management information
  4. align team to common purpose
  5. align team to PI objectives
  6. provide transparency
    7 provide management information
118
Q

What does the team commit to during IP planning

A
  1. do the work
  2. other teams
    3.the program
  3. stakeholders
119
Q

What are the scrum master best practices in Iteration Planning?

A
  1. Maintain timebox
  2. Ensure team commits
  3. Ensure no overcommittment
  4. Challenge team to exceed previous accomplishment
  5. Ensure retropective improvements are implemented
  6. Ensure time for technical debt
120
Q

What are 6 scrum master anti-patterns for Iteration Planning?

A
  1. to technical discussions
  2. Unrealistic commitments
  3. Capacity and load are the exactly the same.
  4. Too worried about technical role
  5. Team undercommits
  6. No time for support activities
121
Q

What are the 3 questions asked at the daily standup?

A
  1. what did you do yesterday
  2. What will you do today
  3. any blockers
122
Q

What are 4 root causes for poor daily stand ups?

A
  1. Poor collaboration
  2. Lack of collective ownership
  3. Infrequent integration
  4. Unreloved conflict
123
Q

What charts does SAFE recommend?

A

Burn up charts

124
Q

What are two problems with burndown charts?

A
  1. Focus on task completed
  2. Cannot distinguish between work not done and work added
125
Q

What are the 6 scrum master best practices for tracking iteration progress?

A
  1. Facilitate mid PI re-planning
  2. Encourage early any potential misses
  3. Encourage use of engineeering practices
  4. ensure defects are not pushed to the IP iteration
  5. facilitate for the the pi
  6. support release activities
126
Q

What are 3 scrum master anti-patterns for tracking iteration progress

A
  1. Team get no input from scrum of scrums
  2. Teams are unwilling to change or add objectives mid-PI
  3. Does all the synchronization
127
Q

What are the 5 scrum master best practices for backlog refinement

A
  1. maintain timeboxes
  2. Maintain deep backlog and ready backlog
  3. ensure participation
  4. invite sme
  5. hold at regular times
128
Q

What are 5 scrum master anti-patterns for backlog refinement?

A
  1. having not ready stories
  2. not consitently refining backlog
  3. team see stories for the first time during interation
  4. feature estimations impact story estimation
129
Q

What is the benefit of an iteration review?

A
  1. demonstrates working software
130
Q

What is demoed during the iteration review?

A

every story, spike, refactor

131
Q

Who attends a demo?

A

team and stakeholders

132
Q

What are the 5 scrum master best practices for system demos?

A
  1. Consider demo during iteration plannign
  2. ensure right participants are present
  3. ensure team celebrates
  4. ensure all team members demo
  5. ensure team is ready for system demo
133
Q

what are 6 scrum master anti-patterns for system demos?

A
  1. too much time preparing the demo
  2. demo is all slides
  3. PO sees things for the first time in the team demo
  4. system demo not done because team demo was enough
    5 team members not invited to system demo
  5. demos are not relevant to art stakeholders
134
Q

What are the 3 scrum master best practices for improvement?

A
  1. Encourage improvement between retrospectives
  2. Coach team on problem solving
  3. take good notes
135
Q

What is the CALMR approach to dev ops?

A

Culture
Automation
Lean flow
Measurement
Recovery

136
Q

Who leads the PI system demo?

A

Product management, POS System team

137
Q

What are the 5 scrum master best practices for inpect and adapt (retro)

A
  1. facilitate the team preparation
  2. provide data
  3. facilitate one of the team in problem solving workshop
  4. help rte ensure improvement items are in PI
  5. Scrum masters may only be parcitipants
138
Q

What are 5 scrum master anti patterns for inspect and adapt

A
  1. only the PO presents
  2. no actionalble improvements
  3. improvements don’t enter pi planning
  4. scrum master too focused on technical
  5. improvement are not demoed.

SAFe Training Cert DONE (1 decks)

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