Scrum PSM I Flashcards
(120 cards)
1
Q
Scrum Definition
Scrum definition?
A
A** lightweight framework**
that **helps **people, teams and organizations generate
value for complex problems trough adaptive solutions
2
Q
Scrum Definition
Scrum requires a Scrum Master
to foster an environment where:
A
- A Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
- Repeat
3
Q
Scrum Definition
Is Scrum itself complex or complete?
Yes / No
A
No, Scrum is simple.
It’s framework is purposefully incomplete, only defining required parts to implement it, as
it’s built upon the collective intelligence of the people using it.
Rather than providing detailed instructions, the Scrum rules guide relationships and interactions.
4
Q
Scrum Definition
Are tools and methodologies
(such as like burn-downs, burn-ups, or cumulative flows)
rescribed?
Yes / No
A
No. Various practices, techniques and methods eixist to forecast progress.
Scrum wraps around existing practices or renders them unnecessary when making the relative efficacy of current management, environment, and work techniques visible.
While proven useful, they don’t replace empiricism.
In complex environments, what will happen is unknown.
Only what has already happened may be used for forward-looking decision making.
5
Q
Scrum Definition
What’s a scrum artifact?
A
Artifacts represent work or value.
They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation.
Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:
● For the Product Backlog it is the Product Goal.
● For the Sprint Backlog it is the Sprint Goal.
● For the Increment it is the Definition of Done.
6
Q
Scrum Theory
“Scrum is founded on empiricism and lean thinking”, means:
A
- Empiricism asserts that knowledge comes from experience and decision-making is based on what’s observed.
- Lean asserts waste is reduced by focusing on the essentials.
7
Q
Scrum Theory
What approach to
problem solving has Scrum?
A
An iterative, incremental approach to optimize predictability and to control risk.
It engages groups of people who collectively have all the skills and expertise to do the work and share or acquire those skills as needed.
8
Q
Scrum Theory
How’s the scrum flow structured?
A
Scrum combines four formal events for inspection and adaptation within a “container event”, the Sprint.
These events are effective because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.
9
Q
Scrum Theory
The three pillars of Scrum are:
A
Transparency
Inspection
Adaptation
10
Q
Scrum Theory
The pillar Transparency means:
A
The emergent process and work must be visible to those performing the work as well as those receiving the work. Artifacts that have low transparency can lead to decisions that diminish value and increase risk.
Transparency enables inspection. Inspection without transparency is misleading and wasteful.
11
Q
Scrum Theory
The pillar Adaption means:
A
If any deviations outside acceptable limits are noticed in inspection, adjustments must be made asap.
Adaptation become difficult when people are not empowered or self-managing.
A Scrum Team is expected to adapt the moment it learns anything new through inspection.
12
Q
Scrum Values
The five scrum values are:
A
- Focus
- Openness
- Respect
- Commitment
- Courage
13
Q
Scrum Values
Focus
A
The Scrum Team and its stakeholders are open about the work and the challenges
14
Q
Scrum Values
Openness
A
The Scrum Team and its stakeholders are open about the work and the challenges
15
Q
Scrum Value
Respect
A
Scrum Team members respect each other to be
**capable, independent people, **
and are respected as such by the people they work with.
16
Q
Scrum Values
Commitment
A
The Scrum Team commits to achieving its goals and to supporting each other
17
Q
Scrum Values
Courage
A
Scrum Team members have the courage to do the right thing,
to work on tough problems.
18
Q
Scrum Team
What is the typical size for a Scrum Team?
A
10 or fewer
19
Q
Scrum Theory
The pillar Inspection means:
A
Artifacts and progress toward goals must be inspected frequently to detect undesirable variances or problems.
Scrum provides its specific cadence in the form of its five events for this.
Inspection enables adaptation. Inspection without adaptation is considered pointless.
Scrum events are designed to provoke change.
20
Q
Scrum Team
All scrum teams will have
a scrum master and product owner
A
True. Outcomes are affected by their level of participation and availability
21
Q
Scrum Team
The fundamental unit of Scrum,
the Scrum Team,
consists of:
2 items
A
- 1Scrum Master
- 1 Product Owner
- Developers
22
Q
Scrum Team
Scrum Teams are:
3 items
A
- Cross-functional, so that team members have all the skills necessary to create value each Sprint.
- Self-managing, so they internally decide who does what, when, and how.
- A cohesive unit without sub-teams / hierarchies focused on one objective at a time (Product Goal)
- Small enough to remain nimble while large enough to complete significant work within a Sprint (~10 or fewer people)
23
Q
Scrum Team
The Scrum Team is responsible for:
A
All product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. They are structured and empowered by the organization to manage their own work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency.
24
Q
Scrum Team
If Scrum Teams become too large…
A
… they should reorganizing into multiple cohesive Scrum Teams, each focused on the same product.
Therefore, they’d should share the same Product Goal, Product Backlog, and Product Owner.
25
# Scrum Team
The entire Scrum Team is accountable for:
Creating valuable, useful increment every Sprint.
26
# Scrum Team
The Scrum Master and Product Owner accountabilities
an be held by one person
True
27
# Scrum Team
Which three specific accountabilities
within the Scrum Team does Scrum define?
1. Developers
2. Product Owner
3. Scrum Master
28
# Scrum Team Developers
Developers are always accountable for:
| 4 items
1. Creating a plan for the Sprint, the Sprint Backlog;
2. Instilling quality by adhering to a Definition of Done;
3. Adapting their plan each day toward the Sprint Goal; and,
4. Holding each other accountable as professionals.
29
# Scrum Team Developers
How much work must the Developers complete for each Sprint?
Enough to meet "Done" with the increment.
30
# Scrum Team Developers
Who is responsible for managing the progress of work during a Sprint?
The Developers.
31
# Scrum Team Developers
The Developers should have all the skills needed to:
Turn the Product Backlog into an increment towards a valuable product.
32
# Scrum Team Developers
When does a Developer become the sole owner of an item on the Sprint Backlog?
Never. All items in the Sprint Backlog are "owned" by the Developers on the Scrum Team.
33
# Scrum Team Developers
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?
Never. The entire Scrum Team is accountable for creating value every Sprint.
34
# Scrum Team Developers
When should a Developer on a Scrum Team be replaced?
As needed, while taking into account a short-term reduction in productivity.
35
# Scrum Team Product Owner
Which statement best describes a Product Owner's responsibility?
Maximizing the value of the product resulting
from the work of the Scrum Team.
36
# Scrum Team Product Owner
Is there a prescribed way how the Product Owner should
maximize the value of the product resulting from the work of the Scrum Team?
No. How this is done may vary widely
across organizations, Scrum Teams, and individuals.
37
# Scrum Team Product Owner
The Product Owner is always accountable for:
| 4 items
1. Developing and explicitly communicating the Product Goal
2. Creating and clearly communicating Product Backlog items
3. Ordering Product Backlog items
4. Ensuring that the Product Backlog is transparent, visible and understood.
38
# Scrum Team Product Owner
Does the Product Owner
have to do all the work by himself?
| 4 items
No. He may delegate the responsibility to others - regardless, the Product Owner remains accountable
39
# Scrum Team Scrum Master
The Scrum Master
is accountable for:
| 4 items
* **Establishing Scrum as defined in the Scrum Guide by helping everyone** in the organization **understand Scrum theory and practice**.
* **The Scrum Team's effectiveness**, so they enable the team to improve its practices within the Scrum framework.
40
# Scrum Team Scrum Master
The Scrum Master serves
the Scrum Team with:
| 4 items
1. Coaching the team's self-management and cross-functionality
2. Helping the team focus on creating high-value increments that meet the definition of done
3. Removing impediments to the teams progress
4. Ensuring that all scrum events take place and are positive, productive and kept within timebox
41
# Scrum Team Scrum Master
The Scrum Master serves
the Product Owner with:
| 4 items
1. Finding techniques for effective product goal definition and backlog management
2. Helping the team understand the need for clear ans concise backlog items
3. Helping establish empirical product planning for a complex environment
4. Facilitating stakeholder collaboration
42
# Scrum Team Scrum Master
The Scrum Master serves
the Organization with:
| 4 items
1. Leading, training and coaching its scrum adoption
2. Planning and advising scrum implementations
3. Helping employees and stakeholders understand and enact an empiricaal approach for complex work
4. Removing barriers between stakeholders and scrum teams
43
# Scrum Events - General
Which Scrum events are timeboxed?
| 3 items
Sprint Planning.
Sprint Review
Sprint Retro
44
# Scrum Events - The Sprint
What is a Sprint?
* Fixed events of one months or less (for more learning cycles and limited cost / effort risks) that are the heartbeat of Scrum, where ideas are turned into value
* Where all the work necessary to achieve the Product Goal (Sprint Planning, Daily Scrums, Sprint Review, Sprint Retrospective) happens, so they can be considered short projects
* Sprints enable predictability by ensuring inspection and adaptation towards the Product Goal
45
# Scrum Events - The Sprint
When does the next Sprint begin?
Immediately after the conclusion of the previous Sprint.
46
# Scrum Events - The Sprint
During the Sprint:
| 4 items
1. No changes are made that would endanger the Sprint Goal
2. Quality does not decrease
3. The Product Backlog is refined as needed
4. Scope may be clarified and renegotiated with the Product Owner as more is learned
47
# Scrum Events - The Sprint
When is a Sprint concluded?
When the
Sprint Retrospective
is complete.
48
# Scrum Events - The Sprint
The CEO asks the Developers to add a "very important" item to a Sprint that is in progress.
What should the Developers do?
Discuss the item with the other members of the Scrum Team so the team can decide what to do.
49
# Scrum Events - The Sprint
Who's responsible for
montoring progress during a sprint?
The Developers.
The create and manage the backlog and use the daily to inspect progress woward the sprint goal while adapting the sprint backlog as necessary.
50
# Scrum Events - The Sprint
When might a Sprint be cancelled?
When the Sprint Goal becomes obsolete.
Only the Product Owner has the authority to cancel the Sprint.
51
# Scrum Events - The Sprint
The length of a Sprint should be:
| 3 items
* Short enough to keep the business risk acceptable
* Short enough to synchronize the development work with other business events.
* One months or less
52
# Scrum Events - The Sprint
The purpose of a Sprint is to produce a valuable and useful Increment of a usable product.
| True / False
True
53
# Scrum Events - Sprint Planning
What's the purpose
of Sprint Planning?
| 3 items
Laying out the work to be performed for the Sprint
This plan is collaborative work of the entire Scrum Team.
They can invite other people to attend Sprint Planning to provide advice.
54
# Scrum Events - Sprint Planning
What are the topics discussed
at Sprint Planning?
| 3 items
The Product Owner ensures everyone's prepared to discuss the **most important Product Backlog items** and how they map to the Product Goal by asking:
1. Why is this Sprint valuable?
2. What can be Done this Sprint?
3. How will the chosen work get done?
55
# Scrum Events - Sprint Planning
What is the Sprint Backlog?
| 7 items
1. The Sprint Goal (The **Why**) as commitment / single objective of the sprint
2. The Product Backlog items selected for the Sprint (The **What**)
3. The Plan for delivering the increments (The **How**)
4. It's a plan by and for the Developers.
5. It's a highly visible, real-time picture of the work of the Sprint to reach the Sprint Goal.
6. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned.
7. It should have enough detail that they can inspect their progress in the Daily Scrum
56
# Scrum Events - Sprint Planning
The Sprint Backlog is fully formulated in the Sprint Planning and does not change during the Sprint.
False.
If the work turns out to be different than the Developers expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint **without affecting the Sprint Goal**.
57
# Scrum Events - Sprint Planning
The timebox for a Sprint Planning event is?
8 hours for a monthly Sprint.
For shorter Sprints it is usually shorter.
58
# Scrum Events - Sprint Planning
During sprint planning all product backlog items **must be** decomposed to a definite set of tasks for the developers
False.
While this can be done it's not mandatory.
How this is done is at the sole discretion of the Developers.
No one else tells them how to turn Product Backlog items into Increments of value.
59
# Scrum Events - The Daily
What' the purpose of the Daily Scrum?
| 2 items
1. To inspect progress toward the Sprint Goal
2. To adapt the Sprint Backlog as necessary
3. To improve communication, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings (while it's not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning work)
60
# Scrum Events - The Daily
Why is the Daily Scrum
held at the same time and same place?
The consistency reduces complexity.
61
# Scrum Events - The Daily
What's the format of the Daily Scrum?
| 3 items
1. It's a 15-minute event for the Developers
2. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers
3. The Developers can select whatever structure and techniques they want, as long as their Daily focuses on progress towards the Sprint Goal and produces an actionable plan for the next day of work.
62
# Scrum Events - The Daily
Who is required to attend the Daily Scrum?
The Developers.
63
# Scrum Events - The Daily
The Scrum Master must facilitate the daily scrum
False. The Daily is an event for the Developers and they are self organized
64
# Scrum Events - The Sprint Review
The **purpose** of the sprint review is?
| 2 items
1. To inspect the outcome of the Sprint as presented by the scrum team to key stakeholders **while an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.**
2. To determine future adaptations as progress toward the Product Goal is discussed.
65
# Scrum Events - The Sprint Review
The **result** of the sprint review is?
Attendees collaborate on what to do next and the Product Backlog may be adjusted to meet new opportunities.
66
# Scrum Events - The Sprint Retro
What's the purpose of the Sprint Retro?
1. To plan ways to increase quality and effectiveness.
2. The Scrum Team inspects how the last Sprint went respective individuals, interactions, processes, tools, and their Definition of Done (inspected elements vary with the work).
3. Misleading assumptions are identified and their origins explored.
4. **What went well **, **what problems were there**, **how were they (not) solved** is discussed.
5. Most impactful improvements are addressed asap - maybe even by addig them to the Sprint Backlog for the next Sprint.
67
# Scrum Events - The Sprint Review
The timebox for the Sprint Review is:
3 hours for a monthly Sprint.
For shorter Sprints it is usually shorter.
68
# Scrum Events - The Sprint Retro
The Scrum Team must choose at least one high prio process improvement item, identified during the Sprint Retro, and put it in the Sprint Backlog.
False
69
# Scrum Events - The Sprint Retro
The Product Owner must invite
stakeholders to the Sprint Retro
False
70
# General
It's mandatory that a product increment is released to prod at the end of each Sprint.
False
71
# General
What is the Definition of Done?
| 4 items
1. A formal description of the state of the Increment when it meets the quality measures required for the product.
2. The moment a Product Backlog item meets the Definition of Done, an Increment is born.
3. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.
4. The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.
72
# General
Who creates the Definition of Done?
| 2 items
1. If DoD is part of the conventions, standards or guidelines of the organization, all Scrum Teams must follow it as a minimum.
2. If there's no standard definition the Development Team must define a DoD appropriate for the product.
3. If there are multiple Scrum Teams working on the product release, the development teams on all of the Scrum Teams must mutually define the DoD.
2. Work cannot be considered part of an Increment unless it meets the Definition of Done.
73
# General
What is velocity?
The amount of
**product backlog
turned into an increment
during a sprint**
74
# General
What is the Product Goal?
1. The Product Goal describes a future state of the product which can serve as a target for the Scrum Team
2. The Product Goal is in the Product Backlog.
3. The rest of the Product Backlog emerges to define "what" will fulfill the Product Goal
75
# General
What's the Product Backlog?
| 3 items
1. An emergent, ordered list of what's needed to improve the product.
2. It's the single source of work undertaken by the Scrum Team.
3. Product Backlog items that can be "Done" within one Sprint are ready for selection in a Sprint Planning event.
76
# General
What is Product Backlog refinement?
1. The act of breaking down and further defining Product Backlog items into smaller, more precise items.
2. This is an ongoing activity to add details, such as a description, order, and size.
3. The Developers are responsible for the sizing. The Product Owner may help them understand the items and select trade-offs.
77
# General
How's the Product Backlog ordered?
The Product Owner
however it's appropriate
78
# General
What are three
incorrect, untrue, or misleading statements
about Scrum?
* Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment.
* Scrum is like traditional processes but with self-organization to replace Project Managers.
* Scrum is a framework that eliminates complexity.
79
# General
What is a benefit of working with timeboxing?
It shifts the focus on getting things done instead of increasing WIP
80
# General
An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?
| 3 items
* Without new vocabulary as reminder of the change, very little change may happen.
* The organization may not understand what has changed with Scrum
* Management may feel less anxious
81
# General
What is a Product?
A product is a vehicle to deliver value.
It has a clear boundary, known stakeholders, well-defined users or customers.
A product could be a service, a physical product, or something more abstract.
82
# General
What's an Increment?
A concrete stepping stone toward the Product Goal.
Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.
In order to provide value, the Increment must be usable.
Multiple Increments may be created within a Sprint.
The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.
Work cannot be considered part of an Increment unless it meets the Definition of Done.
83
How should a Development Team deal with non-functional requirements?
Ensure every Increment meets them
84
What are two effective ways for the Scrum Team to make non-functional requirements visible?
1. Add them to the Product Backlog to ensure transparency.
2. Add them to the definition of Done so the work is taken care of every Sprint.
85
During Sprint Planning the Product Owner and the Developers are unable to reach an understanding about the highest order Product Backlog items.
Because of this, the Developers are unable to determine how many Product Backlog items they can forecast for the upcoming Sprint.
However, the Product Owner and the Developers are able to agree on a Sprint Goal.
Which of the following actions should the Scrum Master support?
Forecast the Product Backlog items that are most likely to meet the Sprint Goal and create the Sprint Backlog. Conclude Sprint Planning and start the development work. Continue to analyze, decompose, and create additional functionality during the Sprint.
During the next Sprint Retrospective discuss why this happened and what changes will make it less likely to recur.
86
All the Scrum Teams working on the same product should have the same Sprint length.
False.
Scrum does not require having aligned Sprints for multiple teams.
87
Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do?
Make sure the Sprint Backlog for the next Sprint includes at least one high priority process improvement.
88
The structure of the Daily Scrum is well-defined and constant. Every team member should answer the three main questions:
What did I do yesterday?
What will I do today?
Do I see any impediment?
False. There is no any prescribed structure. The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. It is still perfectly fine to use the questions, but other ways of conducting the meeting are also possible.
89
What part of the capacity of the Development Team does Product Backlog refinement usually consume?
Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team.
90
What are the three main qualities the team model in Scrum is designed to optimize?
Flexibility
Creativity
Productivity.
91
What are the Scrum Artifacts?
Product Backlog
Sprint Backlog
Increment
92
What is the only way for a Scrum Team to deliver product value?
To release a product Increment
93
What is the essence of Scrum?
| 2 items
1. The essence of Scrum is a small team of people.
2. The individual team is highly flexible and adaptive.
94
What happens when a Sprint is cancelled?
1. Any completed and “Done” Product Backlog items are reviewed
2. If part of the work is potentially releasable, the Product Owner typically accepts it
3. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog
95
What are three Product Backlog features?
1. A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements.
2. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.
3. As long as a product exists, its Product Backlog also exists.
96
Who is responsible for coping with incomplete artifact transparency?
The Scrum Master.
S/he works with the Scrum Team and the organization to increase the transparency of the artifacts.
This work usually involves learning, convincing, and change.
97
What is the Cone of Uncertainty?
A concept that illustrates the reduction of uncertainty regarding project scope as work progresses through sprints.
Initially, there is a high level of uncertainty about the project's requirements and outcomes, but as the team completes sprints, this uncertainty decreases, leading to a clearer understanding of the project's scope and risks.
98
What does Product Backlog management include?
1. Clearly expressing Product Backlog items
2. Ordering the items in the Product Backlog to best achieve goals and missions
3. Optimizing the value of the work the Development Team performs
4. Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next
5. Ensuring the Development Team understands items in the Product Backlog to the level needed.
99
How does the
Definition of Done
help the Scrum Team?
1. DoD is used to assess when work is complete on the product Increment
2. DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning
3. DoD ensures artifact transparency
100
In which two meetings can people outside the Scrum Team participate?
* The Development Team may invite other people to attend the **Sprint Planning** in order to provide technical or domain advice.
* The Product Owner is responsible for inviting the Key Stakeholders to the **Sprint Review**
101
What is the input to
the Sprint Planning?
* The Product Backlog
* The latest product Increment
* Projected capacity of the Development Team during the Sprint
* Past performance of the Development Team
102
What comprises Scrum?
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules
103
Who is responsible for monitoring progress toward high-level goals?
The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal.
104
Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less?
Yes. The Scrum Guide requires only the work planned for the first days of the Sprint is decomposed by the end of the Sprint Planning, often to units of one day or less.
However, 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.
105
What does the word “development” mean in the context of Scrum?
When the words “develop” and “development” are used in the Scrum Guide, they refer to complex work including software and hardware development, development and releasing of products and enhancements, development and sustaining product operational environments, research and identifying of viable markets and technologies, and even more.
106
107
In which meetings are
the Key Stakeholders
allowed to participate?
Only in the Sprint Review.
However, any member of the Scrum Team can interact with them any time.
108
What belongs solely to the Development Team?
The Sprint Backlog.
Only the Development Team can change its Sprint Backlog during a Sprint.
The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and **it belongs solely to the Development Team.**
109
Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?
The Product Owner
110
During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast.
Who should be present to review and adjust the Product Backlog items selected?
The Product Owner and
the Developers
111
How does Scrum help mitigate risk?
The best way to reduce risk is by building small Increments and releasing as often as possible to get feedback, so every Sprint should at least produce one working and releasable increment.
112
Which of the following are valid reasons for the Scrum Master to attend Daily Scrum?
The Scrum Master doesn't attend the Daily. The Daily Scrum is a meeting for the Developers. The Scrum Master has no role in this meeting.
113
Which of the following services is appropriate
for a Scrum Master in regard to the Daily Scrum?
Teach the Developers to keep the Daily Scrum within the 15 minute timebox.
The Scrum Master ensures that the Developers have the event, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only members participate in the Daily Scrum.
114
A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:
There is no acceptable reason.
A new Sprint starts immediately after the conclusion of the previous Sprint.
115
To what extent does technical debt limit the value a Product Owner can get from a product?
| 2 items
1. The velocity at which new functionality can be created is reduced when you have technical debt.
2. Technical debt causes a greater percentage of the product's budget to be spent on maintenance of the product.
116
You release your product to customers once every month, which is better than any competitor. Most of the features you deliver are simply minor changes or corrections to existing features, but customer satisfaction remains low. To improve the competitiveness of your product, what Key Value Areas should be your focus?
1. Unrealized Value.
2. Ability to Innovate.
117
You want to improve your team’s Ability to Innovate. Which of the following actions might help?
1. Set a time of day to be out of meetings to increase focus.
2. Improve the cross-functional skills of your team.
3. Reduce the number of product variants.
118
Your company has many unique variations of the same product that it sells to different customers. Maintaining all these versions leaves you no time to improve the product.
What measure(s) should you examine to help you to improve your ability to deliver value?
1. Velocity
2. Innovation Rate
3. Cycle Time
4. Revenue per Employee
119
Your company is considering investing in a large agile transformation.
What should you measure to know if your initiative is successful?
Customer outcome
120
Measuring the number of times per day a team switches tasks or is interrupted will help you to better understand which Key Value Areas?
1. Ability to Innovate
2. Time to Market
