SAFe Core Values are the fundamental beliefs that guide behaviors and decision-making in SAFe

(Scaled Agile Framework). They are critical for fostering a culture that supports Lean-Agile principles.

Transparency:

Definition: Transparency in SAFe means having an open and honest environment where everyone has

access to the information they need. It involves making work visible to all stakeholders, sharing risks,

and ensuring that everyone understands the status of the work.

Importance: Transparency enables trust across the Agile Release Train (ART) because it ensures that

everyone is aware of what is happening, leading to informed decision-making and reducing

misunderstandings. It builds a culture of openness and accountability.

SAFe Framework Reference: In SAFe, transparency is crucial for effective collaboration and alignment

across teams and stakeholders. It ensures that progress, challenges, and changes are communicated

openly, fostering trust and collective problem-solving.

SAFe Scrum Master Reference:

SAFe training materials emphasize the importance of transparency as a core value that underpins

trust and collaboration within and across teams.

The SAFe website and guides detail how transparency is implemented through various practices like

visual management, open communication, and regular feedback loops.

The program predictability measure is the primary metric used during the quantitative measurement

part of the Inspect and Adapt (I&A) event in SAFe. This measure assesses how reliably the Agile

Release Train (ART) can deliver business value within the Program Increment (PI) timebox. It helps to:

Evaluate the team's ability to meet their commitments.

Identify areas where predictability can be improved.

Ensure that the business value planned for the PI is actually delivered.

By focusing on the predictability of business value, organizations can better align their planning and

execution efforts, ultimately enhancing customer satisfaction and achieving strategic goals more

effectively.

SAFe Scrum Master Reference

SAFe Inspect and Adapt events

SAFe 5.0 framework: using program predictability as a key metric to assess and improve ART

performance.

When a team struggles with breaking down large stories into smaller ones, the Scrum Master can

coach them by demonstrating specific story-splitting techniques. This hands-on approach provides

practical examples of how large stories can be decomposed into smaller, more manageable tasks.

Techniques might include splitting by workflow steps, by business rules, by user roles, or by data

boundaries. By using a specific example, the Scrum Master can illustrate the process and benefits,

helping the team develop this essential skill.

SAFe Scrum Master Reference

SAFe Agile Principles: continuous delivery of value

SAFe 5.0 framework: techniques for effective story splitting

One of the key responsibilities of a Scrum Master is to help the team stay focused on their Iteration

goals. This involves removing any obstacles or impediments that may hinder their progress. By

eliminating impediments, the Scrum Master ensures that the team can work more efficiently and

effectively, thereby maintaining their focus on achieving the goals set for the iteration.

Steps to eliminate impediments include:

Regularly communicating with the team to identify any obstacles they are facing.

Collaborating with stakeholders and other teams to resolve issues quickly.

Ensuring that any identified impediments are documented and tracked until they are resolved.

Facilitating problem-solving sessions and using techniques such as root cause analysis to address

underlying issues.

By proactively removing these barriers, the Scrum Master supports the team in maintaining a steady

and uninterrupted workflow, which is crucial for meeting iteration goals.

SAFe Scrum Master Reference

SAFe Scrum Master Role and Responsibilities

The 2020 Scrum Guide: Scrum Guide 2020

Principles of Lean-Agile Leadership in SAFe: focusing on continuous improvement and supporting the

team in overcoming obstacles.

Utilization refers to the percentage of a team's capacity that is being used. When team members are

highly utilized (i.e., their capacity is nearly fully booked), it often leads to longer lead times. This is

because:

High utilization reduces the team's flexibility to handle new or unexpected work.

It can cause bottlenecks as individuals or teams become overburdened with tasks.

There is less room for managing variability, leading to delays and increased cycle times.

In contrast, lower utilization rates typically allow for more flexibility and quicker response times,

reducing lead times. Therefore, higher utilization generally results in longer lead times due to

increased bottlenecks and reduced capacity to handle new tasks efficiently.

SAFe Scrum Master Reference

SAFe Advanced Scrum Master learning materials

Principles of Lean-Agile development: optimizing flow by managing queue lengths and reducing

batch sizes to improve lead times and throughput.