Launch Agile Release Trains (ARTs)

This five-day program is intended for those larger enterprises who need to apply lean and agile development practices in order to increase the productivity, quality, value delivery and strategic alignment of their software and systems development.

  • Build a predictable model for program increment planning, objective setting, program execution and adaptive feedback that provides a continuous flow of value to the user or marketplace.
  • Train up to 125 team members (typically organized into 8-12 Scrum teams for a common program) in the principles of Scaled Agile Framework and the implementation of SAFe for Teams in an enterprise context.
  • Align the teams to a common enterprise mission and product backlog, and plan for the Program Increment (PI, 8-12 weeks of value) through software and solutions. Establish iteration plans and measurable PI objectives.
  • Introduce prospective Product Owners and Scrum Masters to the principles and practices unique to their role in the Lean-Agile enterprise.






SAFe for Teams SAFe for Teams Program Increment planning: Mission, Vision, and preliminary planning. Program Increment planning continues. Final plan review. SAFe Product Owner Orientation
SAFe for Teams SAFe for Teams Draft plan and management review. Commitment SAFe Scrum Master Orientation

DAY 1: SAFe for Teams

Introducing the Scaled Agile Framework
Building an Agile Team
Planning the Iteration

DAY 2: SAFe for Teams

Executing the Iteration
Executing the PI

DAYS 3 & 4

This portion of the week is a collaborative two-day planning session designed to provide a common vision, mission and joint commitment to a set of achievable Program Increment (PI) objectives. All teams plan 3-5 sprints (6-10 weeks of work) based on the current product and architectural vision. Draft iteration plans are reviewed by management, scope and resource adjustments are made, and teams continue planning until they reach a converged and agreed-to set of business objectives.

DAY 5: SAFe Product Owner Orientation

In Scrum the Product Owner represents the voice of the customer and plays the key role in building and prioritizing the teams product backlog. In this short module, those who will be playing that role on the Scrum team are introduced to the basic practices of the role – backlog development, story writing, prioritizing value, accepting stories into the baseline and working with the team.

DAY 5: Scrum Master Orientation

The Scrum Master’s primary job is to help the team deliver on its objectives by facilitating and monitoring progress, removing impediments, acting as a buffer between the team and any distracting influences and enforcing the rules of Scrum. In this module, individuals who have been selected to fulfill this role will be introduced to the philosophy, activities, practices and challenges that are unique to the role.