Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Scaled Agile
  5. SAFe-SASM

Scaled Agile SAFe-SASM Exam
SAFe Advanced Scrum Master (Page 2 )

Updated On: 1-Feb-2026
Page 2 of 13
PDF with 60 Questions

What are two timestamps required to measure lead time when using a Team Kanban board? (Choose two.)

  1. When the Story is released to users and validated
  2. When the Story is deployed
  3. When the Agile Team pulls a Story onto the board
  4. When the Story is accepted by the Product Owner
  5. When the team completes validation of the Story

Answer(s): C,D

Explanation:

In SAFe (Scaled Agile Framework), lead time is an essential metric used to measure the efficiency and effectiveness of a process. Lead time is defined as the total time it takes for a work item to move through the entire process from the moment it is initiated until it is completed. To measure lead time accurately using a Team Kanban board, two specific timestamps are crucial:
When the Agile Team pulls a Story onto the board (Timestamp C):
This is the starting point of the lead time. It marks the moment when the team commits to working on a particular story by pulling it into the workflow. This action indicates that the story is now in progress and the clock starts ticking from this point.
When the Story is accepted by the Product Owner (Timestamp D):
This is the endpoint of the lead time. It signifies that the story has been completed to the satisfaction of the team and has met the acceptance criteria defined by the Product Owner.
When the Product Owner accepts the story, it indicates that the work is done and the lead time measurement stops.

These two timestamps effectively capture the duration a story takes to go through the development process, providing valuable insights into process efficiency and identifying areas for improvement.
SAFe Scrum Master Reference
SAFe Advanced Scrum Master learning materials
SAFe 5.0 Scrum Master Certification resources
The 2020 Scrum Guide: Scrum Guide 2020
This information aligns with the principles and practices outlined in the SAFe framework and the Scrum Guide, ensuring a comprehensive understanding of lead time measurement within a Team Kanban board context.



What is a Product Owner (PO) anti-pattern in Iteration planning?

  1. The PO introduces the business intent to the team for the first time
  2. The PO changes priorities of the already refined intent
  3. The PO brings in changes to the planned Features based on stakeholder feedback from the System Demo
  4. The PO asks the team for recommendations on Story slicing

Answer(s): A

Explanation:

Anti-Pattern Iteration Planning should not be the first time the team hears about the business intent of the work they are about to start. This should have been communicated earlier through backlog refinement sessions and ongoing interactions with the Product Owner (PO). Business Intent Communication: The PO should regularly update the team on the business context and intent behind backlog items to ensure alignment and readiness for Iteration Planning. Impact: Introducing business intent for the first time during Iteration Planning can lead to confusion, inadequate preparation, and a rushed planning session, which undermines the effectiveness of the iteration.
SAFe Scrum Master


Reference:

SAFe emphasizes the importance of continuous backlog refinement and clear communication of business intent to ensure that teams are well-prepared for Iteration Planning.



What is one action the Scrum Master can take to help the team achieve transparency?

  1. Hold team members accountable to complete their tasks by monitoring task progress deviation
  2. Enforce Agile event timeboxes and working agreements
  3. Be aligned with Product Management when reviewing the Team's Backlog
  4. Ensure team velocity and WIP are a true representation of what is happening within the team

Answer(s): D

Explanation:

Transparency: Ensuring that metrics like team velocity and work in process (WIP) accurately reflect the team's actual work provides visibility into the team's progress and capacity. Action by Scrum Master: By monitoring and ensuring these metrics are accurate, the Scrum Master helps the team maintain transparency about their work, which is critical for making informed decisions and identifying areas for improvement.
Outcome: Accurate representation of velocity and WIP helps the team and stakeholders understand the team's performance, plan effectively, and address any issues promptly.
SAFe Scrum Master


Reference:

SAFe stresses the importance of transparency in Agile teams, and accurate tracking of key metrics like velocity and WIP is a fundamental aspect of achieving this.



Which statement is true about work in process (WIP)?

  1. WIP should be managed by the team's capacity allocation
  2. WIP visibility increases cross-training opportunities
  3. More WIP leads to slower throughput
  4. Limits on WIP prevent visibility into bottlenecks

Answer(s): C

Explanation:

WIP (Work in Process): Refers to the number of work items that are in progress at any given time. Impact of High WIP: Having too many items in progress can lead to context switching, inefficiencies, and delays, ultimately slowing down the overall throughput of the team. Throughput: The rate at which the team completes work items. Reducing WIP helps the team focus on completing tasks, leading to faster throughput and better flow of work.
SAFe Scrum Master


Reference:

SAFe emphasizes limiting WIP to improve flow efficiency, reduce bottlenecks, and increase throughput.



How is team performance calculated in SAFe?

  1. The ratio of tasks planned to tasks completed
  2. The ratio of business value achieved to business value planned for the PI
  3. The ratio of Story points completed to Story points planned in the PI
  4. Team member utilization as a percentage of total capacity

Answer(s): C

Explanation:

Team Performance Measurement: In SAFe, one of the key metrics for measuring team performance is the ratio of Story points completed to Story points planned in the Program Increment (PI). Story Points: Represent the effort required to complete user stories. By comparing planned and completed Story points, teams can gauge their ability to deliver on commitments. Purpose: This metric helps in assessing how well the team is performing relative to their planned objectives, identifying areas for improvement, and making adjustments for future PIs.
SAFe Scrum Master


Reference:

SAFe provides guidance on using Story points and other metrics to measure team performance and drive continuous improvement.



Viewing page 2 of 13
Viewing questions 6 - 10 out of 60 questions



Post your Comments and Discuss Scaled Agile SAFe-SASM exam prep with other Community members:

Join the SAFe-SASM Discussion