Scrum Roles Events and Artifacts Flashcards

1
Q

What are the three Scrum events?

A

Reviews
Planning
Retrospective

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

What three roles are recognized in Scrum?

A

Scrum Master
Product Owner
Development Team

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

What is the job of a Scrum Master?

A

Servant Leader
Facilitator of Development Team
Process Coach
Impediment remover

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

What is the job of a Product Owner?

A

Provides vision and direction to the team

Prioritizes the requirements for team

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

What is the job of a Development Team?

A

Comprises of 10 developers

Makes efforts to meet goals set by PO

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

Scrum Master Do’s

A

is a servant leader who helps the team achieve success
facilitator of scrum events (sprint planning, daily stand-up)
an impediment remover (like always having to seek approvals)
is the process coach for the team

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

Scrum Master Don’ts

A

not to be a figure of authority under any circumstances
should not be the task master of the team (micro manage, assign tasks, as for daily status, chase people down)
will not be a technical or design authority for the team

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

What are some important skills and attributes of a good Scrum Master?

A

Collaborative, knowledgeable, humble, influential, committed, patient.

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

What are the two roles of a Product Owner?

A

Vision and Boundaries

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

Product owner creates a product vision with several inputs such as:

A

customers
technical team
executive
SME’s

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

Product owner creates a product vision with several inputs such as:

A

Sets expectations with stakeholders for delivery milestones and roadmap
Establishes acceptance criteria

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

To be successful, a product owner must be:

A

available, business savvy, excellent communicator, decisive, empowered.

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

True or False

The PO rarely makes decisions?

A

False

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

True or False

The scrum master ought to be decisive in decision making

A

False

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

True or False

Neither the PO or Scrum Master should have reporting authority over the Development Team

A

True

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

True or False

The PO represents the interests of stakeholders in the product

A

True

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

True or False

A scrum master may have to push back against unrealistic goals set by a “pushy” PO

A

True

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

True or False

Over time, the scrum master becomes less busy whereas the PO becomes busier?

A

True

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

Agile teams have three distinguishing characteristics which are:

A

Small
Cross-functional
Self-organizing

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

True or False

Small teams are favorable, as it is more productive

A

True

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

True or False

Scrum teams adjust better to component teams.

A

False

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

True or False

Component teams are NOT favored in scrum teams

A

True

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

What are some advantages of feature teams over component teams?

A
Evaluate design decision impact
Reduces waste by hand-offs
Ensures right people are talking 
No risk to schedule
Focuses on feature delivery
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

In a Scrum team, the project manager’s duties are taken care by different roles. What responsibilities does a PO ingest from a PM?

A

Road maps
Release plans
Stakeholder engagement

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

In a Scrum team, the project manager’s duties are taken care by different roles. What responsibilities does a Scrum Team ingest from a PM?

A

Estimation
Planning
Day-to-day task management

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

True or False

The Scrum Master takes over the role of establishing the process and advising the team

A

True

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

True or False

Scrum makes no distinction for the different specialist positions in the Development Team.

A

True

Architects, UX designers, Testers are all viewed as part of the team.

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

Product Owners are responsible for the W** in the delivery of each increment

A

What

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

The Development Team is responsible for the H** in the delivery of each increment

A

How

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

A sprint is synonymous with __________.

A

iteraction

31
Q

A sprint is a _______ event between one to _____ weeks.

A

timebox, 4

32
Q

The goal for a sprint should be a complete and releasable product. Which encompasses ________ and _______.

A

Development

Testing

33
Q

True or False

Sprint duration and deliverables should not change once it has been planned.

A

True

34
Q

What should occur in the first day of a Sprint

A

Iteration Preparation

35
Q

What should occur in the second day of a Sprint

A

Iteration Planning

36
Q

What should occur in next to the last day of a Sprint

A

Demo Preparation

37
Q

What Team event occurs at the last day of a sprint?

A

Retrospective

38
Q

The backlog refinement (grooming) process includes:

A

Discovering and describing items
Prioritizing the backlog
Sizing the backlog items
Getting ready for planning the next sprint

39
Q

The steps followed in a Scrum methodology are:

A

Sprint Planning
Daily stand-up
Sprint review
Sprint retrospective

40
Q

Who ought to attend a Sprint Planning meeting?

A

Developer
Product Owner
Scrum Master

41
Q

During Sprint Planning, whose responsible for:

Underline the goals of the sprint
Clarify open questions
Take priority decisions

A

Product Owner

42
Q

During Sprint Planning, whose responsible for:

Facilitating the meeting

A

Scrum Master

43
Q

During Sprint Planning, whose responsible for:

Plan the sprint in as much detail as possible

A

Team

44
Q

During Sprint Planning, what two approaches are there to determine the workload?

A

Velocity-Driven

Commitment-Driven

45
Q

If a team doesn’t have enough past data (sprints) to determine work load, what could they begin with?

A

Start with the commitment-driven approach: decisions based on discussions and willingness to commit.

46
Q

True or False

Team buy-in is important regardless of what Sprint Planning work load is decided upon.

A

True

47
Q

_________ is a measure of the amount of work that the team can do in a given sprint or iteration.

A

Velocity

48
Q

Steps involved in a velocity-driven approach to sprint planning are:

A
Adjust priority
Determine the target velocity
Identify an iteration goal
Select the user stories
Split the user stories
Estimate tasks
49
Q

In a commitment-driven sprint planning event, the team adds stories to the backlog _____________ aligned with a sprint goal.

A

one at a time

50
Q

Various failure modes of sprint planning are:

A
Too aggressive or too conservative
Inability to reach consensus
Not considering known events
Not enough preparation
Search for elusive certainty
51
Q

True or False

Scrum Master must let the team justify their commitment without any influence.

A

True

52
Q

a meeting described as:

OF THE TEAM, FOR THE TEAM, and BY THE TEAM is what meeting?

A

Daily Scrum

53
Q

Daily Scrum Meeting agenda asks?

A

What happened yesterday
What is planned for today
What issues are blocking progress

54
Q

Who ought to attend the Sprint Review event?

A

Developers
PO
Scrum Master
interested stakeholders

55
Q

What is the only event (meeting) that individuals NOT in the Scrum team can attend?

A

The Sprint Review

56
Q

Who should attend a Sprint Retrospective event? (1hr)

A

Development team

Scrum Master

57
Q

The purpose of the sprint retrospective is to:

A

Make issue visible
Come up with improvement opportunities
Take ownership of the actions

58
Q

True or False

A Scrum master should facilitate the Spring Retrospective and make people want to attend.

A

True

59
Q

Failure modes of Sprint Review:

A
Inadequate preparation
Too many or too few external invitees
Team members getting too defensive
Too much discussion
Discussing retrospective or next sprint planning
60
Q

Various failure modes of sprint retrospective are:

A
Temptation to skip
Fatigue of the team
Tendency to point fingers
Presence of external stakeholders
Too much attention to negatives
61
Q

The definition of Done answers the question ___________.

A

What does success look like!

62
Q

The definition of Ready answers the question _________________.

A

Are we ready to start working on a product backlog item?

63
Q

An item is ready to be worked on only if:

A
64
Q

______ is any work item that the team can do to add value to the customer.

A

Backlog

65
Q

New requirements relevant to product keeps the ___________ evolving.

A

product backlog.

66
Q

Release backlogs is a subset of the?

A

product backlog

67
Q

Sprint backlog is a subset of a _______________ containing all the work to be completed in a sprint.

A

release backlog

68
Q

Backlog content comprises of:

A
69
Q

Backlog content comprises of:

A
70
Q

Desirable characteristics of a product backlog can be described as:

DEEP

A

Detailed appropriately
Estimated
Emergent
Prioritized

71
Q

The ‘D’ in DEEP describes

A

items with higher priority are provided with more details

72
Q

The first ‘E’ in DEEP describes

A

Estimates are expressed as story points of ideal days.

73
Q

The second ‘E’ in DEEP describes

A

Emergent - backlog items can be added, moved, modified, or removed as required by the customer.

74
Q

The ‘P’ in DEEP describes

A

All product backlog items must be prioritized