SAFe for Government: Roles and Responsibilities

Bridge the gap between bureaucracy and agility.

Agile work in government can be quite challenging due to long-standing bureaucratic processes and outdated labor categories that hinder the flexibility required to manage Agile acquisitions. Our latest micro-credential course aims to bridge the gap between traditional staff competencies and the new Agile roles that are needed to manage large complex systems at scale.


SAFe for Government: Roles and Responsibilities empowers you to navigate and overcome bureaucratic challenges, fostering the agility needed to manage large-scale, complex systems. By learning from industry experts and engaging in real-world problem-solving, you will gain the confidence and skills to lead and innovate in your government role.

What will I learn?

  • Summarize the most important agile roles and practice key agile activities through the lens of government work
  • Identify mitigation strategies to the most common SAFe adoption and transformation challenges
  • Become a lean-agile leader in a government context

What is a SAFe Micro-credential course?

A new training product from Scaled Agile meticulously designed to bridge the gap between theory & practice, providing actionable insights in a blended learning experience that combines a self-paced eLearning with a half-day, expert-facilitated session focusing on real-world simulations, not slides.

What should I expect before, during, and after my course?

Before
Complete 1 hour e-learning
Prior to attending your facilitated session, we highly recommend completing the associated e-learning in SAFe Studio. This e-learning provides the perfect preparation for your facilitated session.

During
Engage in 4-hour facilitated session
During your live session, a facilitator will help guide you and your classmates through a variety of activities and workshops designed to not only provide knowledge, but provide practical applications of what you learn.

After
Immediately apply your knowledge
Upon completing your e-learning and facilitated session, you will be instantly ready to apply your knowledge in your unique setting.

What is the course curriculum?

“>Self-paced, on-demand eLearning (1 hour)
The eLearning module provides a comprehensive overview of the responsibilities of key agile roles including Business Owner, Product Owner (PO), Scrum Master/Team Coach (SM/TC), Product Manager, Release Train Engineer (RTE), System Architect, and SAFe Practice Consultant (SPC), as well as the concept of Customers and end users in a government context. Several lessons and four self-reflection activities provide the perfect preparation for your facilitated session.

Activity 1 – Key Agile Roles in Government (~55 minutes)
To fully understand agile roles in government, you need to start with the SAFe concept of Flow. This activity reviews the eight properties of flow-based systems before discussing the activities, decisions, and other aspects of several agile roles and responsibilities.

Activity 2 – Activities of Agile Roles in Government (~45 minutes)
PI Planning is an integral event within SAFe. Our second activity provides hands-on experience assigning PI cycle activities to the appropriate role, teaching participants to identify shared activities and dependencies between roles and activities, including how to incorporate additional government requirements into the cycle.

Activity 3 – Government Scenario (~27 minutes)
Executive orders are commonplace in a government context — and often disrupt planned work. This activity reviews the options for addressing an executive order that disrupts planned work by teaching participants to identify who is involved in replanning work and developing and communicating a strategy when plans need to change.

Activity 4 – Anti-patterns & The Changing Role of Government Leadership (~65 minutes)
With more than a decade of agile transformations, we understand the typical challenges that can impede an agile acquisition. This discussion based activity helps agilists operating in a government context prevent or mitigate common challenges that run counter to Lead-Agile practices.