15 Topics
10 Days
Programme Overview
Training Description
Who Should Attend
- Team leaders and supervisors
- Project and programme managers
- Departmental and functional managers
- HR and organisational development professionals
- Team coaches and facilitators
- Business and operations managers
- Project team members
- Change management professionals
- Employee engagement and workplace culture specialists
- Professionals responsible for workplace safety and wellbeing
Session Objectives
- Understand the SAFe Lean-Agile mindset
- Learn the roles of a SAFe team member
- Discover how to apply SAFe principles and practices
- Master the mechanics of a Program Increment (PI)
- Learn to write and decompose user stories
- Participate effectively in PI Planning
- Understand the team's role in the Agile Release Train (ART)
- Collaborate with other teams to deliver solutions
- Master iteration execution and System Demos
- Understand the importance of Inspect and Adapt (I&A)
About the Course
The Elevating Team Performance: Safe For Teams Training Course is designed to help teams create safer, more collaborative, productive, and high-performing work environments. The course explores practical approaches to psychological safety, effective communication, teamwork, trust-building, conflict management, accountability, and collaborative problem-solving.
Participants will learn how to identify behaviours and workplace conditions that undermine team performance and apply strategies that encourage openness, mutual respect, constructive feedback, and shared responsibility. The training also equips team leaders and managers with practical tools for building resilient teams where employees feel confident contributing ideas, raising concerns, taking appropriate risks, and learning from mistakes.
Curriculum & Topics
15 Topics | 10 Days
-
Subtopic 1.1:
The importance of enterprise agility
-
Subtopic 1.2:
The four configurations of SAFe
-
Subtopic 1.3:
The SAFe House of Lean and its principles
-
Subtopic 1.4:
An overview of the Agile Release Train (ART)
-
Subtopic 1.5:
Key terminology and roles in SAFe
-
Subtopic 2.1:
The structure and purpose of a SAFe team
-
Subtopic 2.2:
The roles of Product Owner, Scrum Master, and team members
-
Subtopic 2.3:
The importance of cross-functional teams
-
Subtopic 2.4:
Team responsibilities in the ART
-
Subtopic 2.5:
Team collaboration and self-organization
-
Subtopic 3.1:
The Agile Manifesto and its core values
-
Subtopic 3.2:
SAFe Principles as a foundation for teams
-
Subtopic 3.3:
The importance of continuous learning and improvement
-
Subtopic 3.4:
Applying Lean principles to team workflow
-
Subtopic 3.5:
The role of servant leadership within the team
-
Subtopic 4.1:
The purpose and agenda of PI Planning
-
Subtopic 4.2:
The team's role in preparing for the event
-
Subtopic 4.3:
Participating in breakout sessions and drafting plans
-
Subtopic 4.4:
Communicating team objectives and dependencies
-
Subtopic 4.5:
The importance of PI objectives and team commitment
-
Subtopic 5.1:
Understanding the PI timeline and cadence
-
Subtopic 5.2:
The role of the team in System Demos
-
Subtopic 5.3:
The Scrum of Scrums and ART Sync meetings
-
Subtopic 5.4:
The importance of team-level ceremonies
-
Subtopic 5.5:
The role of the team in Inspect and Adapt (I&A)
-
Subtopic 6.1:
The purpose of iteration planning
-
Subtopic 6.2:
Daily stand-ups and their importance
-
Subtopic 6.3:
Tracking progress and managing the Team Kanban board
-
Subtopic 6.4:
The role of the Product Owner in the iteration
-
Subtopic 6.5:
The importance of the Iteration Review
-
Subtopic 7.1:
The relationship between Features and Stories
-
Subtopic 7.2:
Writing effective user stories and acceptance criteria
-
Subtopic 7.3:
The INVEST model for good stories
-
Subtopic 7.4:
Decomposing features into manageable stories
-
Subtopic 7.5:
Collaborating with the Product Owner on the Team Backlog
-
Subtopic 8.1:
The importance of a definition of done
-
Subtopic 8.2:
Applying test-driven development (TDD)
-
Subtopic 8.3:
The role of the team in continuous integration
-
Subtopic 8.4:
Automating tests for faster feedback
-
Subtopic 8.5:
The importance of team-level quality practices
-
Subtopic 9.1:
The purpose and agenda of the System Demo
-
Subtopic 9.2:
The team's role in preparing for the demo
-
Subtopic 9.3:
Demonstrating working functionality to stakeholders
-
Subtopic 9.4:
Gathering feedback and incorporating it into the next iteration
-
Subtopic 9.5:
The System Demo as a key event in the PI
-
Subtopic 10.1:
The purpose of the I&A workshop
-
Subtopic 10.2:
The three parts of the workshop: PI System Demo, Quantitative Measurement, Retrospective
-
Subtopic 10.3:
The team's role in generating improvement ideas
-
Subtopic 10.4:
The importance of creating and executing improvement stories
-
Subtopic 10.5:
The I&A as a driver of continuous improvement
-
Subtopic 11.1:
The role of the team in the Continuous Delivery Pipeline (CDP)
-
Subtopic 11.2:
Understanding Continuous Integration and Continuous Deployment
-
Subtopic 11.3:
The importance of Built-In Quality
-
Subtopic 11.4:
How the team contributes to the release process
-
Subtopic 11.5:
The team's role in DevOps culture
-
Subtopic 12.1:
The responsibilities of the Scrum Master and Product Owner
-
Subtopic 12.2:
How the team collaborates with these roles
-
Subtopic 12.3:
The PO's role in providing a clear vision
-
Subtopic 12.4:
The Scrum Master's role as a servant leader and coach
-
Subtopic 12.5:
The team's responsibility to support the PO and Scrum Master
-
Subtopic 13.1:
The importance of cross-team communication
-
Subtopic 13.2:
Resolving dependencies and impediments with other teams
-
Subtopic 13.3:
The role of the Scrum of Scrums
-
Subtopic 13.4:
Shared understanding and alignment across the ART
-
Subtopic 13.5:
The importance of a unified team approach
-
Subtopic 14.1:
The principle of self-organizing teams
-
Subtopic 14.2:
The team's role in managing its own work
-
Subtopic 14.3:
The importance of autonomy and mastery
-
Subtopic 14.4:
Empowering teams to make decisions
-
Subtopic 14.5:
The team's role in creating a safe and productive environment
-
Subtopic 15.1:
Understanding how the team's role fits into the larger SAFe picture
-
Subtopic 15.2:
How the team interacts with the Release Train Engineer (RTE)
-
Subtopic 15.3:
The team's relationship with System and Solution Architects
-
Subtopic 15.4:
The importance of stakeholder communication
-
Subtopic 15.5:
The role of the team in the overall Lean-Agile transformation
