Professional Scrum Flashcards

You may prefer our related Brainscape-certified flashcards:
1
Q

What are the 3 roles that makeup a Scrum Team?

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

What is Scrum?

A

Scrum is a framework for managing projects

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

True or False

Scrum is a methodology or process

A

False

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

What is empiricism?

A

Empiricism is the theory that knowledge is derived from experience

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

What is lean?

A

Lean is a way of thinking about creating value with less waste

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

What is agile?

A

Agile is a project management approach that embodies the values and principles written in the agile manifesto

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

What are the 4 agile values?

A

Value:
1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. customer collaboration over contract negotiation
4. Responding to change over following a plan

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

How should you think about Agile and Scrum?

A

Agile is the specification, Scrum is the implementation

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

What are the 3 Scrum pillars?

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

What is a product goal?

A

A product goal is the desired future state of a product

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

What is a product backlog?

A

A product backlog is an ordered list of items needed to create and maintain a product

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

True or False

The product goal is in the product backlog

A

True

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

Who is accountable for the effective management of the product backlog?

A

The product owner

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

Can a product owner delegate the management of the product backlog to others?

A

Yes, but the product owner is still ultimately accountable for the effective management of the product backlog

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

What are the 5 scrum values?

A
  • Commitment
  • Focus
  • Openness
  • Respect
  • Courage
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is technical debt?

A

Technical debt is the unpredictable cost for implementing sub-optimal solutions. Technical debt can be intentional or unintentional and is usually the result of time/business constraints

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

What is DevOps?

A

DevOps is the combination of software development and IT operations

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

What is a stakeholder?

A

A stakeholder is an entity with an interest in the product. A stakeholder is external to the scrum team

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

Who represents the stakeholders?

A

The product owner

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

True or False

Within a Scrum Team, there are no sub-teams

A

True

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

What is the typical size of a scrum team?

A

10 or fewer people

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

Who is accountable for creating a valuable, useful Increment every Sprint

A

The scrum team

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

What is an increment?

A

An increment is functional piece of software that meets the definition of done

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

True or False

The product owner is a committee, not a person

A

False

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
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
26
Q

How long is a sprint?

A

1 month or less

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

Who has the authority to cancel a sprint if the sprint goal becomes obsolete?

A

The product owner

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

True or False

The sprint planning requires the collaborative work of the entire scrum team

A

True

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

True or False

The scrum team cannot invite other people to the sprint planning to provide advice

A

False

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

True or False

The sprint goal requires the collaboration of the entire scrum team

A

True

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

When must the sprint goal be finalized?

A

The sprint goal must be finalized before the sprint planning ends

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

What is a forecast?

A

A forecast is the selection of PBIs developers believe they can complete during a sprint

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

What is the maximum amount of time that can be allocated to the sprint planning for a 1 month sprint?

A

8 hours

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

What are the 3 components of the sprint backlog?

A
  • Sprint goal
  • PBIs selected for the sprint
  • Plan for delivering the work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

What is the purpose of the daily scrum?

A

The purpose of the daily scrum is to inspect the progress towards the sprint goal and to adapt accordingly. The work for the next 24 hours is also planned during the daily scrum

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

Who must attend the daily scrum?

A

Developers

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

What is the purpose of the sprint review?

A

To inspect and present the increment(s). Attendees collaborate on what to do next

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

What is the maximum amount of time that can be allocated to the sprint review for a 1 month sprint?

A

4 hours

39
Q

What is the maximum amount of time that can be allocated to the sprint retrospective for a 1 month sprint?

A

3 hours

40
Q

What are the 3 scrum artifacts?

A
  • Product backlog
  • Sprint backlog
  • Increment
41
Q

What are the associated commitments for each of the 3 scrum artificats?

A
  • Product backlog = product goal
  • Sprint backlog = sprint goal
  • Increment = definition of done
42
Q

What is product backlog refinement?

A

Product backlog refinement is the process of breaking down PBIs into smaller items

43
Q

True or False

The scrum team must fulfill or abandon a product goal before taking on the next one

A

True

44
Q

Who is accountable for effective management of the sprint backlog?

A

The developers

45
Q

True or False

The sprint goal is in the sprint backlog

A

True

46
Q

Can multiple increments be created within a single sprint?

A

Yes

47
Q

True or False

An increment may not be delivered before the end of the sprint

A

False

48
Q

True or False

A Product Backlog item that does not meet the Definition of Done cannot be released or even presented at the Sprint Review

A

True

49
Q

When does a developer become accountable for delivering an increment for a sprint?

A

Never. The entire scrum team is accountable for delivering an increment for a sprint

50
Q

What is ATDD?

A

Acceptance test-driven development is a development methodology where failing acceptance tests are written before any other code is written

51
Q

What is a build?

A

A build is a potentially releasable unit of software. It is the result of converting source code into an executable

52
Q

When using ATDD, in addition to meeting acceptance criteria, is it a good practice to also test unhappy paths?

A

Yes

53
Q

What is TDD?

A

Test-driven development is a development methodology where failing test cases are written before any other code is written. TDD follows the red-green-refactor cycle

54
Q

What is unit testing?

A

Unit testing is the testing of small, isolated units of code. The definition of a “unit” depends on the context and should be agreed upon by the developers

55
Q

False

Passing acceptance tests is equivalent to the PBI being Done

A

False

Having passing acceptance tests only proves that the acceptance criteria have been satisfied. It does not necessarily mean that all aspects of the Definition of Done have been completely satisfied. Other items might have to be completed, such as creating documentation or a release note

56
Q

True or False

CI/CD can be done without automated testing

A

False

57
Q

What is regression testing?

A

Regression testing is the rerunning of previously successful tests. These could be tests from previous sprints

58
Q

True or False

ATDD helps developers build the right thing while TDD helps developers build it right

A

True

59
Q
  1. What is a spike?
  2. What is its purpose?
A
  1. A spike is a small development experiment.
  2. Its purpose is to help developers obtain the knowledge necessary to forecast PBIs
60
Q

If an organization does not have a definition of done, who must create it for a product?

A

The scrum team

61
Q

What is last responsible moment?

A

LRM is the strategy of delaying a decision until the moment the cost of not making the decision is greater than the cost of making it

62
Q

What is the difference between continuous delivery and continuous deployment?

A

Continuous delivery requires some form of human action for releasing to production while continuous deployment does not (all automated)

63
Q

What is continuous delivery?

A

Continuous deliver is the practice of delivering software in short cycles

64
Q

Who is accountable for creating a product goal?

A

Product owner

65
Q

Who is accountable for creating product backlog items?

A

Product owner

66
Q

When is an increment born?

A

An increment is born when a product backlog item meets the definition of done

67
Q

When is a forecast given?

A

During the sprint planning

68
Q

When is the sprint backlog created?

A

During the spring planning

69
Q

What is continuous integration?

A

Continuous integration is the practice of continuously committing code changes to a shared repository

70
Q

What is telemetry?

A

Telemetry is the process of recording and transmitting the readings of an instrument

71
Q

What is the difference between coupling and cohesion?

A

Coupling refers to the degree of interdependence between modules. Cohesion refers to the degree of relatedness among the members of a module

The developer should aim for lose coupling and high cohesion

72
Q

True or False

If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, but have different Product Owners

A

False

Product owner should be the same for all scrum teams focusing on the same product

73
Q

What is BDD?

A

Behavior-driven development is a development methodology that extends TDD by describing desired functional behavior

74
Q

What is smoke testing?

A

Smoke testing is the testing of the crucial features of a new build. If the tests are successful, the build is ready for more rigorous testing

75
Q

What is blue-green deployment?

A

Blue-green deployment is a deployment strategy where 2 identical environments are created. 1 runs the application (blue) and 2 tests the new application. Once all tests are successful, all traffic from 1 is directed to 2 and 1 becomes green and 2 becomes blue

76
Q

What is blameless postmortem?

A
77
Q

What tactic should a Scrum Master use to divide a group of 100 people into multiple Scrum Teams?

A

Ask the people to divide themselves into teams

78
Q

What are the 3 ways of DevOps?

A
  1. Maximize flow
  2. Amplify feedback loops
  3. Continuous learning
79
Q

When is Performance Testing most effectively performed?

A

Often, throughout development of the Software

80
Q

What is a function point?

A

A function point is a unit of measurement to estimate the cost of software as a whole. It is also used as an indicator of the size and complexity of the software

81
Q

True or False

For depth of inheritance, a low value is bad (not easily maintanable) and a high value is good (easily maintainable)

A

False

82
Q

What is cyclomatic complexity?

A

Cyclomatic complexity is a measurement of the amount of decision logic for a given source code

83
Q

What are software architecture quality goals known as?

A

ilities

84
Q

Stakeholders can be included in Product Backlog Refinement?

A

True

85
Q

Who owns the Sprint Backlog?

A

The development team

86
Q

What is YAGNI?

A

YAGNI is the practice of building functionality only when it becomes necessary

87
Q

What is static analysis?

A

Static analysis is the analysis of source code without executing the application

88
Q

What is velocity?

A

Velocity is an indication of the amount of PBIs turned into increments during the sprint

89
Q

What is A/B testing?

A

A/B testing is the testing of 2 versions of a system to determine which performs better

90
Q

What is continuous testing?

A

Continuous testing is the practice of continuously testing an application throughout its software development life cycle

91
Q

What is cycle time?

A

Cycle time is the amount of time it takes to start a PBI and deliver an increment

92
Q

What is feature toggling?

A

Feature toggling is the practice of dynamically toggling specific functionality on or off without affecting overall accessability to the application

93
Q

What is the scout rule?

A

The scout rule is the practice of leaving the code you’re working on a little bit better than how you found it

94
Q

What is a user story?

A

A user story is a description of a software feature written from a user’s perspective