SAFe 4 Practitioner Certification Exam
Graded A+
3 steps in the path of BDD are? - ANS-1) Discovery of behavior
2) Formulation of specific tests
3) Automation of tests
A balance between emergent design and intentional architecture is required for what? -
ANS-Speed of development and maintainability
A story point is a singular number that represents 4 criteria? - ANS-1) Volume: How
much is there?
2) Complexity: How are is it?
3) Knowledge: what do we know?
4) Uncertainty: What's not know?
A team meets their commitments by doing what two key functions? - ANS-1) by doing
everything they said they would do
2) In the event that it is not feasible, they must immediately raise a red flag
After all plans had been presented, remaining what are discussed and categorized? -
ANS-Program risks and impediments
After dependencies are resolved and risks are addressed what is taken next? - ANS-
Confidence vote is taken at the Team and Program Levels
After the Teams conduct a short retrospective, then systematically address the larger
impediments that are limiting velocity with what workshop? - ANS-Problem-solving
workshop
As "Iterations" being one of the team planning radiators what would be some of the key
points to call-out? - ANS-1) If a story has a dependency, put a red sticky on it describing
the dependency. Put a check mark through it once the dependency has been
addressed
2) If a risk is broader in nature, put it on the risk sheet
3) If needed, allocate a percentage of capacity for unplanned activities such as
maintenance and production support
As "PI Iteration" being one of the team planning radiators what would be some of the
key points to call-out? - ANS-1) The last Iteration will be used for Innovation and
Planning (PI)
2) You should have a velocity but not a load on the IP Iteration, since it should not
contain any user value stories
,As "PI Objectives" being one of the team planning radiators what would be some of the
key points to call-out? - ANS-1) PI Objectives should be written as SMART objectives
2) Objectives are assigned business value during the second team breakout
3) Stories supporting stretch objectives are included in the load calculation
As "Risks" being one of the team planning radiators what would be some of the key
points to call-out? - ANS-1) Program risks are those that need to be escalated to the
program level. They will be captured and ROAMed after the final plan review
2) Team risks are those under the team's control. They won't be presented.
At Day 1 end, management meets to do what? - ANS-Make adjustments to scope and
objectives based on the day's planning
Based on new knowledge (and a good night's sleep), teams work to create their final
plans during which "Team breakout" session? - ANS-Team breakout session # 2
Before exposing new functionality to users, by a separate deploy to production, we
should do the following? - ANS-Enable testing background and foreground processes in
the actual production environment
Collocation? - ANS-1) enhances productivity
2) critical for agile teams to be effective
3) recommended for programs to have efficient product development flow
Control variability with? - ANS-> Planning cadence (i.e. single interval)
Define a compliance enable story? - ANS-Facilitate specific activities such as
verification and validations, documentation, sing-offs, regulatory submissions and
approvals
Define acceptance criteria? - ANS-1) Acceptance criteria provide the details of the story
from a testing point of view
2) Acceptance criteria are created by the agile team
Define an architecture enabler story? - ANS-Builds the architectural runway, which
enables smoother and faster development
Define an exploration enabler story? - ANS-Builds understanding of what is needed by
the customer, to understand prospective solutions and evaluate alternatives
Define an infrastructure enabler story? - ANS-Builds development and testing
frameworks that enable a faster and more efficient development process
Define Enabler Stories? - ANS-They build the groundwork for future user stories
, Define Solution Features for the Program Backlog? - ANS-1) Features are services that
fulfill user needs
2) Feature is an industry-standard term familiar to marketing and Product Management
3) Expressed as a phrase, value is expressed in terms of benefits
4) Features are identified, prioritized, estimated, and maintained in the Program Backlog
Define the "SMART" format? - ANS-1) Specific - States the intended outcome as
simply, concisely, and explicitly as possible (Hint: Try starting with an action verb)
2) Measurable - It should be clear what a team needs to do to achieve the objective.
The measures may be descriptive, yes/no, quantitative, or provide a range.
3) Achievable - Achieving the objective should be within the team's control and influence
4) Realistic - Recognize factors that cannot be controlled. (Hint: Avoid making "happy
path" assumptions)
5) Time-bound - The time period for achievement must be within the PI, and therefore
all objectives must be scoped appropriately
Define the 3'c? - ANS-1) Card - written on a card or in a tool and may annotate with
notes
2) Conversation - details are in a conversation with the PO
3) Confirmation - Acceptance criteria confirms the story correctness
Define the INVEST model used when writing user stories? - ANS-1) Independent - story
should be independent of all other stories
2) Negotiable - story should only share the why and what but not the how (i.e. solution)
3) Valuable - story should add value to a customer that uses the feature,
product/solution
4) Estimable - story should provide enough information to be understood by the team
and estimated
5) Small - story should be small enough in size to be completed in as little time as
possible (i.e. few weeks to a few days)
6) Testable - story should be understood enough by the team as to define them (i.e.
acceptance criteria)
Define the Team Backlog? - ANS-1) Contains all the work the team needs to work on
2) Created by the PO/Team
3) Prioritized by PO
4) Contains user and enabler stories
- User stories provide Customers with value
- Enabler stories build the infrastructure and architecture that makes user stories
possible
5) NFRs are constraints on the backlog
Describe the "Break out a spike" technique when splitting a user story - ANS-1) A story
or feature may not be understood well enough to estimate. Build a technical or
functional spike to figure it out, then split the story based on that result
2) Sometimes the team needs to develop a design, or prototype an idea
Graded A+
3 steps in the path of BDD are? - ANS-1) Discovery of behavior
2) Formulation of specific tests
3) Automation of tests
A balance between emergent design and intentional architecture is required for what? -
ANS-Speed of development and maintainability
A story point is a singular number that represents 4 criteria? - ANS-1) Volume: How
much is there?
2) Complexity: How are is it?
3) Knowledge: what do we know?
4) Uncertainty: What's not know?
A team meets their commitments by doing what two key functions? - ANS-1) by doing
everything they said they would do
2) In the event that it is not feasible, they must immediately raise a red flag
After all plans had been presented, remaining what are discussed and categorized? -
ANS-Program risks and impediments
After dependencies are resolved and risks are addressed what is taken next? - ANS-
Confidence vote is taken at the Team and Program Levels
After the Teams conduct a short retrospective, then systematically address the larger
impediments that are limiting velocity with what workshop? - ANS-Problem-solving
workshop
As "Iterations" being one of the team planning radiators what would be some of the key
points to call-out? - ANS-1) If a story has a dependency, put a red sticky on it describing
the dependency. Put a check mark through it once the dependency has been
addressed
2) If a risk is broader in nature, put it on the risk sheet
3) If needed, allocate a percentage of capacity for unplanned activities such as
maintenance and production support
As "PI Iteration" being one of the team planning radiators what would be some of the
key points to call-out? - ANS-1) The last Iteration will be used for Innovation and
Planning (PI)
2) You should have a velocity but not a load on the IP Iteration, since it should not
contain any user value stories
,As "PI Objectives" being one of the team planning radiators what would be some of the
key points to call-out? - ANS-1) PI Objectives should be written as SMART objectives
2) Objectives are assigned business value during the second team breakout
3) Stories supporting stretch objectives are included in the load calculation
As "Risks" being one of the team planning radiators what would be some of the key
points to call-out? - ANS-1) Program risks are those that need to be escalated to the
program level. They will be captured and ROAMed after the final plan review
2) Team risks are those under the team's control. They won't be presented.
At Day 1 end, management meets to do what? - ANS-Make adjustments to scope and
objectives based on the day's planning
Based on new knowledge (and a good night's sleep), teams work to create their final
plans during which "Team breakout" session? - ANS-Team breakout session # 2
Before exposing new functionality to users, by a separate deploy to production, we
should do the following? - ANS-Enable testing background and foreground processes in
the actual production environment
Collocation? - ANS-1) enhances productivity
2) critical for agile teams to be effective
3) recommended for programs to have efficient product development flow
Control variability with? - ANS-> Planning cadence (i.e. single interval)
Define a compliance enable story? - ANS-Facilitate specific activities such as
verification and validations, documentation, sing-offs, regulatory submissions and
approvals
Define acceptance criteria? - ANS-1) Acceptance criteria provide the details of the story
from a testing point of view
2) Acceptance criteria are created by the agile team
Define an architecture enabler story? - ANS-Builds the architectural runway, which
enables smoother and faster development
Define an exploration enabler story? - ANS-Builds understanding of what is needed by
the customer, to understand prospective solutions and evaluate alternatives
Define an infrastructure enabler story? - ANS-Builds development and testing
frameworks that enable a faster and more efficient development process
Define Enabler Stories? - ANS-They build the groundwork for future user stories
, Define Solution Features for the Program Backlog? - ANS-1) Features are services that
fulfill user needs
2) Feature is an industry-standard term familiar to marketing and Product Management
3) Expressed as a phrase, value is expressed in terms of benefits
4) Features are identified, prioritized, estimated, and maintained in the Program Backlog
Define the "SMART" format? - ANS-1) Specific - States the intended outcome as
simply, concisely, and explicitly as possible (Hint: Try starting with an action verb)
2) Measurable - It should be clear what a team needs to do to achieve the objective.
The measures may be descriptive, yes/no, quantitative, or provide a range.
3) Achievable - Achieving the objective should be within the team's control and influence
4) Realistic - Recognize factors that cannot be controlled. (Hint: Avoid making "happy
path" assumptions)
5) Time-bound - The time period for achievement must be within the PI, and therefore
all objectives must be scoped appropriately
Define the 3'c? - ANS-1) Card - written on a card or in a tool and may annotate with
notes
2) Conversation - details are in a conversation with the PO
3) Confirmation - Acceptance criteria confirms the story correctness
Define the INVEST model used when writing user stories? - ANS-1) Independent - story
should be independent of all other stories
2) Negotiable - story should only share the why and what but not the how (i.e. solution)
3) Valuable - story should add value to a customer that uses the feature,
product/solution
4) Estimable - story should provide enough information to be understood by the team
and estimated
5) Small - story should be small enough in size to be completed in as little time as
possible (i.e. few weeks to a few days)
6) Testable - story should be understood enough by the team as to define them (i.e.
acceptance criteria)
Define the Team Backlog? - ANS-1) Contains all the work the team needs to work on
2) Created by the PO/Team
3) Prioritized by PO
4) Contains user and enabler stories
- User stories provide Customers with value
- Enabler stories build the infrastructure and architecture that makes user stories
possible
5) NFRs are constraints on the backlog
Describe the "Break out a spike" technique when splitting a user story - ANS-1) A story
or feature may not be understood well enough to estimate. Build a technical or
functional spike to figure it out, then split the story based on that result
2) Sometimes the team needs to develop a design, or prototype an idea
