1
Q
Purpose of the Scrum Guide
A
This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together.
2
Q
What are the 3 Characteristics of the Scrum framework?
A
- Lightweight
- Simple to understand
- Difficult to master
3
Q
What is Empiricism?
A
Empiricism asserts that knowledge comes form experience and making decisions based on that is known.
4
Q
Three pillars of empirical process control
A
transparency, inspection, and adaptation
5
Q
What is Transparency?
A
Significant aspects of the Scrum process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by:
- A common language referring to the scrum process shared by all participants; and.
- Those performing the work and those accepting the work product must share a common definition of “Done”
6
Q
What is Inspection?
A
Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.
- Their inspection should not be so frequent that inspection gets in the way of the work.
- Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.
7
Q
Four formal events for inspection and adaptation
A
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
8
Q
Make up of a Scrum Team
A
Product Owner, the Development Team, and a Scrum Master
9
Q
What are the two primary characteristics of a Scrum Team?
A
- Scrum Teams are self-organizing and cross-functional.
- The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
10
Q
Describe the Product Owner
A
The Product Owner is responsible for maximizing the value of the product and the work of the Development Team.
11
Q
Who is responsible for managing the Product Backlog?
A
The Product Owner
12
Q
What is involved in Product Backlog Management?
A
- Clearly expressing Product Backlog Items;
- Ordering the items in the Product Backlog to best achieve goals and missions;
- Optimizing the value of the work the Development Team performs;
- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
- Ensuring the Development Team understands items in the Product Backlog to the level needed.
13
Q
Who Manages the Product Backlog?
A
The Product Owner may do the work, or have the Development Team do it. However, the Product Owner remains accountable.
14
Q
Characteristics of a Development Team
A
- They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
- Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment;
- Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;
- Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and
- Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
15
Q
Optimal Development Team Size
A
3-9; small enough to remain nimble and large enough to complete significant work within a Sprint.
16
Q
How does the Scrum Master server the Product Owner?
A
- Finding techniques for effective Product Backlog management;
- Helping the Scrum Team understand the need for clear and concise Product Backlog items;
- Understanding product planning in an empirical environment;
- Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
- Understanding and practicing agility; and,
- Facilitating Scrum events as requested or needed.
17
Q
How does the Scrum Master serve the Development Team?
A
- Coaching the Development Team in self-organization and cross-functionality;
- Helping the Development Team to create high-value products;
- Removing impediments to the Development Team’s progress;
- Facilitating Scrum events as requested or neededl and,
- Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
18
Q
How does the Scrum Master serve the Organization?
A
- Leading and coaching the organization in it’s Scrum adoption;
- Planning Scrum implementations within the organization;
- Helping employees and stakeholders understand and enact Scrum and empirical product development;
- Causing change that increases the productivity of the Scrum Team; and,
- Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.
19
Q
What does a time-boxed event mean?
A
Every event has a maximum duration.
20
Q
Ways that a sprint event can end
A
- Event hits the time box or
- It can be cancelled if the Sprint Goals becomes obsolete.
21
Q
What is the heartbeat of Scrum?
A
Sprint
22
Q
What is a Sprint?
A
a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.
23
Q
When does a new Sprint start?
A
A new Sprint starts immediately after the conclusion of the previous Sprint.
24
Q
Scrum has 3 guidelines/rules during a sprint. What are they?
A
- No changes are made that would endanger the Sprint Goal;
- Quality goals do not decrease; and
- Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
25
Advantages of doing work in sprints.
Enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal.
26
Who cancel a sprint?
Only the Product Owner can.
27
Reasons to cancel a Sprint?
The Sprint goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change.
28
What are the steps that occur when a sprint is cancelled?
When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed.
1. If part of the work is potentially releasable, the Product Owner typically accepts it.
2. Al incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. The work done on them depreciates quickly and must be frequently re-estimated.
29
Max duraction for Sprint Planning Meeting?
a maximum of eight hours for a one-month Sprint.
30
Sprint Planning answers the following questions
1. What can be done this Sprint?
1. The Development Team works to forecast the functionality that will be developed during the Sprint.
2. The Scrum Team crafts a Sprint Goal; an objective that wil be met within the Sprint through the implementation of the Product Backlog,
2. How wil the chosen work get done?
1. The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog.
31
What is the Product Backlog?
an ordered list of everything that might be needed in the product and is the single source of requirements of any changed to be made to the product.
32
In a Product Backlog, what 3 things is the product owner is responsible for?
1. content,
2. availability, and
3. ordering
33
Can a Product Backlog be complete?
a Product Backlog is never complete.
34
How long does a Product Backlog last?
As long as a product exists, it's Product Backlog also exists.
35
What 4 attributes must a Product Backlog item have?
Product Backlog items have the attributes of:
1. a description,
2. order,
3. estimate, and
4. value
36
What influences can change a Product Backlog?
Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.
37
What is Product Backlog refinement and what happens during Product Backlog refinement?
Product Backlog refinement is the act of **_adding detail_**, **_estimates_**, and **_order_** to items in the Product Backlog. During Product Backlog refinement, items are viewed and revised.
38
What percentage should refinement take?
Refinement usually consumes no more than 10% of the capacity of the Development Team.
39
Who is responsible for all estimates?
The Development Team.
40
What does it mean a user story is Ready?
1. Can be done within one Sprint
2. Can be deemed for selection in Sprint Planning.
41
At least every ______ total work remaining should be summed.
at least every Sprint Review.
42
What is the Sprint Backlog (4 things)
The Sprint Backlog is
1. The set of Product Backlog items selected for the Sprint,
2. a plan for delivering the product Increment and realizing the Sprint Goal.
3. The forecast by the Development Team about what functionality will be in the next Increment
4. work needed to deliver that functionality into a "Done" Increment.
43
What happens to the Sprint Backlog when new work is discovered/required?
The Development Team adds it to the Sprint Backlog.
44
Who can change the Sprint Backlog during a Sprint?
the Development Team only.
45
How is progress tracked during a Sprint?
By tracking the remaining work throughout the Sprint.
46
In what 4 ways can a Scrum Master detect incomplete transparency?
A Scrum Master can detect incomplete transparency by
1. inspecting the artifacts,
2. sensing patterns,
3. listening closely to what is being said, and
4. detecting differences between expected and real results.
47
What does a team do if "Done" is not a convetion of the development organization?
The Development Team of the Scrum Team must define a definition of done "appropriate for the product".
48
How does team handle the definition of done when there are multiple Scrum Teams?
The Development Teams on all of the Scrum Teams must mutually define the "definition of done".
49
Can I pick and choose from Scrum?
Scrum exists only in it's entirety and functions well as a container for other techniques, methodologies, and practices.
50
What are the 4 inputs to the Sprint Planning meeting?
1. the Product Backlog,
2. the latest product increment,
3. projected capacity of the Development Team during the Sprint, and
4. past performance of the Development Team
51
What is the Sprint Goal?
an objective that will be met withing the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the increment.
52
What should happen by the end of the Sprint Planning meeting?
The Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated increment.
53
What is the Daily Scrum?
a 15 minute time boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.
54
What 3 questions are answered by the Development Team members at the Daily Scrum?
1. What **did i do yesterday** that helped the Development Team meet the Sprint Goal?
2. What **will i do today** to help the Development Team meet the Sprint Goal?
3. Do I see any **impediment** that prevents me or the Development Team from meeting the Sprint Goal?
55
Who is responsible for the Daily Scrum meeting?
The **Scrum Master** ensures that the Development Team _has_ the meeting, but the **Development Team** is _responsible_ for conduction the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15- minute time-box.
56
What is the purpose of the Daily Scrums? (5 points)
1. improve communications,
2. eliminate other meetings,
3. identify impediments to development for removal,
4. highlight and promote quick decision-making, and
5. improve the Development Team's level of knowledge.
57
Why is the Sprint Review held?
to inspect the Increment and adapt the Product Backlog if needed.
58
How long is the Sprint Review Meeting?
It's a 4 hour time-boxed event for one-month Sprints.
59
Who attends the Sprint Review?
Attendees include the Scrum Team and key Stakeholders invited by the Product Owner.
60
What is the purpose of the Sprint Retrospective?
It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted.
61
Whens does the Sprint Retrospective occur?
After the Sprint Review and prior to the next Sprint Planning.
62
How long is the Sprint Retrospective?
a 3 hour time-boxed event for one-month Sprints.
63
Scrum Master's role in the retrospective? (3 items)
1. The Scrum Master ensures that the event takes place and that attendants understand it's purpose.
2. The Scrum Master teaches all to keep it within the time-box.
3. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.
64
The porpose of the Sprint Retrospective?
1. Inspect how the last sprint went with regards to people, relationships, process, and tools
2. Identify and order the major items that went well and potential improvements
3. Create a plan for implementing improvements to the way the Scrum Team doet it work.
65
The Sprint Review includes the following elements: (7 elements)
1. The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done";
2. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
3. The Development Team demonstrates the work that it has "Done" and answers questions about the Increment;
4. The Product Owner discusses the Product Backlog as it stands. He or sche projects likely completion dates based on progress to date (if needed);
5. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
6. Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
7. Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
66
What is Adaptation?
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.
67
What is the Development Team?
The Development Team consist of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint. Only members of the Development Team create the Increment.
68
What is a Scrum Master?
The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.
69
Why can a Sprint only 1 month long?
When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase.
Scrum exam
flashcards
Decks in class (3)
# Cards
