Scrum SAFe-SASM - SAFe Advanced Scrum Master (SASM)

Creating a buffer state between two states in a Kanban board can help regulate the flow of work and address the varying completion times.

Buffer State Purpose:Acts as a holding area to balance the flow between different stages of work, smoothing out variances in completion times.

Flow Regulation:Ensures that work can continue smoothly without bottlenecks or idle times.

Work In Progress (WIP) Limits:Helps maintain a steady flow by preventing too much work from accumulating in any one state.

This approach aligns with Lean principles of managing flow and reducing variability in processes.

SAFe Scrum Master References:

SAFe Advanced Scrum Master Training Material, Chapter on Kanban Systems​​.

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 References:

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

The Portfolio Backlog in SAFe contains the larger initiatives, known as Epics. Epics are substantial pieces of work that require analysis, investment, and development effort over multiple Program Increments (PIs). They represent significant business or technical needs that drive the long-term strategy of the organization. These Epics are prioritized and managed in the Portfolio Backlog, where they can be decomposed into smaller, actionable items as they progress through the development process.

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 References

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.

Cumulative Flow Diagram (CFD):A CFD is a visual tool used in Kanban and Scrum to show the progress of work items through different stages of the workflow over time.

Arrival and Departure Curves:These curves represent the work items entering (arrival) and leaving (departure) the system.

Growing Distance:If the distance between the arrival and departure curves on the CFD is growing apart, it indicates that work items are taking longer to move through the system.

Lead Time:This term refers to the total time from when a work item is created until it is completed. An increasing distance between the curves means that work items are spending more time in the system, thus increasing the lead time.

SAFe Scrum Master References:

SAFe materials on flow metrics and Kanban principles highlight the importance of monitoring lead time and using CFDs to identify bottlenecks and inefficiencies in the workflow.

To transform unpredictable events into predictable events (A): Cadence creates a regular, reliable schedule for events, which helps in managing and mitigating variability. This predictability allows teams to plan and execute their work more effectively, reducing the uncertainty of unforeseen events.

To synchronize planning for multiple teams and ARTs (C): Cadence helps align the planning cycles of multiple teams and Agile Release Trains (ARTs), ensuring that everyone works in a coordinated manner. This synchronization is critical for integrated, cross-team activities and for maintaining a cohesive workflow across the organization.

SAFe Scrum Master References

SAFe Principles: the importance of cadence and synchronization

SAFe 5.0 framework: benefits of applying cadence in Agile teams

Promoting T-shaped skill development means encouraging team members to develop a broad set of skills in addition to their specialization. This enhances team flexibility and resilience.

Pairing on Stories (A):By having team members pair up on stories, knowledge is shared, and members can learn from each other’s expertise. This practice helps in building secondary skills and fosters a collaborative learning environment.

Cross-Functional Stories (E):Defining stories that require cross-functional skills ensures that team members have to work together, leveraging and developing a broader range of skills. This practice helps in cross-training and builds a more versatile team.

These methods help in breaking down silos within the team and promote a culture of continuous learning and skill development.

SAFe Scrum Master References:

SAFe Advanced Scrum Master Training Material, Chapter on Team Dynamics and Collaboration​​​​​​.

The decision to implement pair programming in future iterations is a team-level improvement action that stems from reflecting on their current processes and identifying areas for enhancement. This is best captured during the team's retrospective:

Retrospective Purpose:The retrospective is a regular meeting where the team reflects on what went well, what didn’t, and what could be improved.

Action Items:Decisions and action items, such as adopting pair programming, are documented in the retrospective notes to ensure they are followed up in future iterations.

Continuous Improvement:Capturing this in the retrospective notes ensures the team is committed to continuous improvement and has a clear record of their decisions and plans for process enhancements.

SAFe Scrum Master References:

SAFe Advanced Scrum Master Training Material, Chapter on Team Retrospectives​​.