Professional Scrum Flashcards
(94 cards)
1
Q
What are the 3 roles that makeup a Scrum Team?
A
- Product Owner
- Scrum Master
- Developers
2
Q
What is Scrum?
A
Scrum is a framework for managing projects
3
Q
True or False
Scrum is a methodology or process
A
False
4
Q
What is empiricism?
A
Empiricism is the theory that knowledge is derived from experience
5
Q
What is lean?
A
Lean is a way of thinking about creating value with less waste
6
Q
What is agile?
A
Agile is a project management approach that embodies the values and principles written in the agile manifesto
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
8
Q
How should you think about Agile and Scrum?
A
Agile is the specification, Scrum is the implementation
9
Q
What are the 3 Scrum pillars?
A
- Transparency
- Inspection
- Adaptation
10
Q
What is a product goal?
A
A product goal is the desired future state of a product
11
Q
What is a product backlog?
A
A product backlog is an ordered list of items needed to create and maintain a product
12
Q
True or False
The product goal is in the product backlog
A
True
13
Q
Who is accountable for the effective management of the product backlog?
A
The product owner
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
15
Q
What are the 5 scrum values?
A
- Commitment
- Focus
- Openness
- Respect
- Courage
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
17
Q
What is DevOps?
A
DevOps is the combination of software development and IT operations
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
19
Q
Who represents the stakeholders?
A
The product owner
20
Q
True or False
Within a Scrum Team, there are no sub-teams
A
True
21
Q
What is the typical size of a scrum team?
A
10 or fewer people
22
Q
Who is accountable for creating a valuable, useful Increment every Sprint
A
The scrum team
23
Q
What is an increment?
A
An increment is functional piece of software that meets the definition of done
24
Q
True or False
The product owner is a committee, not a person
A
False
25
What are the 5 scrum events?
* Sprint
* Sprint planning
* Daily scrum
* Sprint review
* Sprint retrospective
26
How long is a sprint?
1 month or less
27
Who has the authority to cancel a sprint if the sprint goal becomes obsolete?
The product owner
28
# True or False
The sprint planning requires the collaborative work of the entire scrum team
True
29
# True or False
The scrum team cannot invite other people to the sprint planning to provide advice
False
30
# True or False
The sprint goal requires the collaboration of the entire scrum team
True
31
When must the sprint goal be finalized?
The sprint goal must be finalized before the sprint planning ends
32
What is a forecast?
A forecast is the selection of PBIs developers believe they can complete during a sprint
33
What is the maximum amount of time that can be allocated to the sprint planning for a 1 month sprint?
8 hours
34
What are the 3 components of the sprint backlog?
* Sprint goal
* PBIs selected for the sprint
* Plan for delivering the work
35
What is the purpose of the daily scrum?
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
36
Who must attend the daily scrum?
Developers
37
What is the purpose of the sprint review?
To inspect and present the increment(s). Attendees collaborate on what to do next
38
What is the maximum amount of time that can be allocated to the sprint review for a 1 month sprint?
4 hours
39
What is the maximum amount of time that can be allocated to the sprint retrospective for a 1 month sprint?
3 hours
40
What are the 3 scrum artifacts?
* Product backlog
* Sprint backlog
* Increment
41
What are the associated commitments for each of the 3 scrum artificats?
* Product backlog = product goal
* Sprint backlog = sprint goal
* Increment = definition of done
42
What is product backlog refinement?
Product backlog refinement is the process of breaking down PBIs into smaller items
43
# True or False
The scrum team must fulfill or abandon a product goal before taking on the next one
True
44
Who is accountable for effective management of the sprint backlog?
The developers
45
# True or False
The sprint goal is in the sprint backlog
True
46
Can multiple increments be created within a single sprint?
Yes
47
# True or False
An increment may not be delivered before the end of the sprint
False
48
# 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
True
49
When does a developer become accountable for delivering an increment for a sprint?
Never. The entire scrum team is accountable for delivering an increment for a sprint
50
What is ATDD?
Acceptance test-driven development is a development methodology where failing acceptance tests are written before any other code is written
51
What is a build?
A build is a potentially releasable unit of software. It is the result of converting source code into an executable
52
When using ATDD, in addition to meeting acceptance criteria, is it a good practice to also test unhappy paths?
Yes
53
What is TDD?
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
What is unit testing?
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
# False
Passing acceptance tests is equivalent to the PBI being Done
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
# True or False
CI/CD can be done without automated testing
False
57
What is regression testing?
Regression testing is the rerunning of previously successful tests. These could be tests from previous sprints
58
# True or False
ATDD helps developers build the right thing while TDD helps developers build it right
True
59
1. What is a spike?
2. What is its purpose?
1. A spike is a small development experiment.
2. Its purpose is to help developers obtain the knowledge necessary to forecast PBIs
60
If an organization does not have a definition of done, who must create it for a product?
The scrum team
61
What is last responsible moment?
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
What is the difference between continuous delivery and continuous deployment?
Continuous delivery requires some form of human action for releasing to production while continuous deployment does not (all automated)
63
What is continuous delivery?
Continuous deliver is the practice of delivering software in short cycles
64
Who is accountable for creating a product goal?
Product owner
65
Who is accountable for creating product backlog items?
Product owner
66
When is an increment born?
An increment is born when a product backlog item meets the definition of done
67
When is a forecast given?
During the sprint planning
68
When is the sprint backlog created?
During the spring planning
69
What is continuous integration?
Continuous integration is the practice of continuously committing code changes to a shared repository
70
What is telemetry?
Telemetry is the process of recording and transmitting the readings of an instrument
71
What is the difference between coupling and cohesion?
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
# 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
False
Product owner should be the same for all scrum teams focusing on the same product
73
What is BDD?
Behavior-driven development is a development methodology that extends TDD by describing desired functional behavior
74
What is smoke testing?
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
What is blue-green deployment?
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
What is blameless postmortem?
77
What tactic should a Scrum Master use to divide a group of 100 people into multiple Scrum Teams?
Ask the people to divide themselves into teams
78
What are the 3 ways of DevOps?
1. Maximize flow
2. Amplify feedback loops
3. Continuous learning
79
When is Performance Testing most effectively performed?
Often, throughout development of the Software
80
What is a function point?
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
# True or False
For depth of inheritance, a low value is bad (not easily maintanable) and a high value is good (easily maintainable)
False
82
What is cyclomatic complexity?
Cyclomatic complexity is a measurement of the amount of decision logic for a given source code
83
What are software architecture quality goals known as?
ilities
84
Stakeholders can be included in Product Backlog Refinement?
True
85
Who owns the Sprint Backlog?
The development team
86
What is YAGNI?
YAGNI is the practice of building functionality only when it becomes necessary
87
What is static analysis?
Static analysis is the analysis of source code without executing the application
88
What is velocity?
Velocity is an indication of the amount of PBIs turned into increments during the sprint
89
What is A/B testing?
A/B testing is the testing of 2 versions of a system to determine which performs better
90
What is continuous testing?
Continuous testing is the practice of continuously testing an application throughout its software development life cycle
91
What is cycle time?
Cycle time is the amount of time it takes to start a PBI and deliver an increment
92
What is feature toggling?
Feature toggling is the practice of dynamically toggling specific functionality on or off without affecting overall accessability to the application
93
What is the scout rule?
The scout rule is the practice of leaving the code you're working on a little bit better than how you found it
94
What is a user story?
A user story is a description of a software feature written from a user's perspective
