SAFE 5 ADVANCED SCRUM MASTER STUDY EXAMS
GUIDE QUESTIONS AND ANSWERS SURE A+
✔✔#4 build incrementally with fast, integrated learning cycles - ✔✔1 - The interative
learning cycle
2 - Reduces the cost of risk-taking by truncating unsuccessful paths quickly
3 - Is facilitated by small batch sizes
4 - The shorter the cycles, the faster the learning
✔✔#5 Base milestones on objective evaluation of working systems - ✔✔1 - Build the
system in increments, each of which is an integration point that demonstrates some
evidence of the feasibility of the solution proccess
2 - Objective milestones facilitate learning and allow for continuous, cost-effective
adjustments towards an optimum Solution
✔✔#6 Visualize and limit WIP, reduce batch sizes, and manage queue lengths - ✔✔1 -
When there's too much WIP, there's no visibility into bottlenecks, and the system is
usually highly inefficient
✔✔How can we reduce lead times? - ✔✔1 - Reduce size of work
2 - Reduce bottlenecks
3 - Reduce waiting
4 - Increase swarming
5 - Improve quality
✔✔The importance of small batches - ✔✔1 - Large batch sizes increase variability
2 - High utilization increases variability
3 - Severe project slippage is the most likely result
4 - The most important batch is the transport
5 - Proximity (co-location) enables small batch size
6 - Good infrastructure enbales small batch size
, ✔✔#7 Apply cadence, synchronize with cross-domain planning - ✔✔1 - All stakeholders
meet face-to-face
2 - Management sets the mission with minimum possible constraints
3 - Requirements and design happen
4 - Important stakeholder decision are acelerated
5 - Teams create and take responsibility for plans
✔✔#8 Unlock the intrinsic motivation of knowledge workers - ✔✔1 - Knowledge workers
have to manage themselves: they need autonomy
2 - Continuing innovation has to be part of the work and the responsibility of knowledge
workers
3 - Workers themselves are most qualified to make decisions about how to perform their
work
✔✔#9 Decentralize decision-making - ✔✔1 - Some decisions are strategic, have far-
reaching impact, and are outside the scope, knowledge, or responsibilities of the teams.
These should be centralized;
2 - Decentralize all others:
2.1 - Frequent decisions
2.2 - Time-critical decisions
2.3 - Decisions that require local information
3 - Define the economic logic behind a decision; empower individuals and teams to
actually make them
✔✔#10 Organize around value - ✔✔1 - A Value Stream is the sequence of steps used
to deliver value to the customer
✔✔Anti-patterns associated with The Product Owner - ✔✔1 - Team has more than one
Product Owner
2 - Partially completed Stories are being carried over from Iteration to Iteration
3 - Developers don't work collaboratively on Stories
4 - Lack of coordination with other teams leads to excessive WIP
✔✔Key responsibilities of the Product Owner - ✔✔1 - Facilitate Team Backlog
refinement
2 - Prepare for and participate in Iteration Planning
3 - Elaborate Stories and Enablers just-in-time
4 - Address team questions; be the voice of the customer
5 - Accept Stories
6 - Participate in the Iteration Review and Retrospective
7 - Coordinate with other Prodcut Owners to manage dependencies
✔✔Big Stories Anti-Patterns - ✔✔1 - Big Stories do not support team Iteration
2 - Smaller Stories allow for faster, more reliable implementation
3 - Splitting bigger stories into smaller ones is an essential skill
GUIDE QUESTIONS AND ANSWERS SURE A+
✔✔#4 build incrementally with fast, integrated learning cycles - ✔✔1 - The interative
learning cycle
2 - Reduces the cost of risk-taking by truncating unsuccessful paths quickly
3 - Is facilitated by small batch sizes
4 - The shorter the cycles, the faster the learning
✔✔#5 Base milestones on objective evaluation of working systems - ✔✔1 - Build the
system in increments, each of which is an integration point that demonstrates some
evidence of the feasibility of the solution proccess
2 - Objective milestones facilitate learning and allow for continuous, cost-effective
adjustments towards an optimum Solution
✔✔#6 Visualize and limit WIP, reduce batch sizes, and manage queue lengths - ✔✔1 -
When there's too much WIP, there's no visibility into bottlenecks, and the system is
usually highly inefficient
✔✔How can we reduce lead times? - ✔✔1 - Reduce size of work
2 - Reduce bottlenecks
3 - Reduce waiting
4 - Increase swarming
5 - Improve quality
✔✔The importance of small batches - ✔✔1 - Large batch sizes increase variability
2 - High utilization increases variability
3 - Severe project slippage is the most likely result
4 - The most important batch is the transport
5 - Proximity (co-location) enables small batch size
6 - Good infrastructure enbales small batch size
, ✔✔#7 Apply cadence, synchronize with cross-domain planning - ✔✔1 - All stakeholders
meet face-to-face
2 - Management sets the mission with minimum possible constraints
3 - Requirements and design happen
4 - Important stakeholder decision are acelerated
5 - Teams create and take responsibility for plans
✔✔#8 Unlock the intrinsic motivation of knowledge workers - ✔✔1 - Knowledge workers
have to manage themselves: they need autonomy
2 - Continuing innovation has to be part of the work and the responsibility of knowledge
workers
3 - Workers themselves are most qualified to make decisions about how to perform their
work
✔✔#9 Decentralize decision-making - ✔✔1 - Some decisions are strategic, have far-
reaching impact, and are outside the scope, knowledge, or responsibilities of the teams.
These should be centralized;
2 - Decentralize all others:
2.1 - Frequent decisions
2.2 - Time-critical decisions
2.3 - Decisions that require local information
3 - Define the economic logic behind a decision; empower individuals and teams to
actually make them
✔✔#10 Organize around value - ✔✔1 - A Value Stream is the sequence of steps used
to deliver value to the customer
✔✔Anti-patterns associated with The Product Owner - ✔✔1 - Team has more than one
Product Owner
2 - Partially completed Stories are being carried over from Iteration to Iteration
3 - Developers don't work collaboratively on Stories
4 - Lack of coordination with other teams leads to excessive WIP
✔✔Key responsibilities of the Product Owner - ✔✔1 - Facilitate Team Backlog
refinement
2 - Prepare for and participate in Iteration Planning
3 - Elaborate Stories and Enablers just-in-time
4 - Address team questions; be the voice of the customer
5 - Accept Stories
6 - Participate in the Iteration Review and Retrospective
7 - Coordinate with other Prodcut Owners to manage dependencies
✔✔Big Stories Anti-Patterns - ✔✔1 - Big Stories do not support team Iteration
2 - Smaller Stories allow for faster, more reliable implementation
3 - Splitting bigger stories into smaller ones is an essential skill
