Scribd
Upload
58 views

Safe

This document discusses the SAFe framework for agile development at the program level. It describes an Agile Release Train (ART) as comprising multiple teams working together to deliver an integrated system over the course of a Program Increment (PI). A PI lasts 8-12 weeks and includes multiple 2-week iterations, with the last used for innovation and planning. The ART delivers a working system increment at the end of each PI through demos and reflection. Larger programs may involve multiple coordinated ARTs.

Uploaded by

Manan Warge
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
58 views

Safe

This document discusses the SAFe framework for agile development at the program level. It describes an Agile Release Train (ART) as comprising multiple teams working together to deliver an integrated system over the course of a Program Increment (PI). A PI lasts 8-12 weeks and includes multiple 2-week iterations, with the last used for innovation and planning. The ART delivers a working system increment at the end of each PI through demos and reflection. Larger programs may involve multiple coordinated ARTs.

Uploaded by

Manan Warge
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 3

Program

This is when multiple teams are working together in a similar fashion as described above, but this time
to deliver an overall system. This amalgamation of teams is called an Agile Release Train (ART), which can
comprise of about 50 - 125 people. For each ART, a Program Increment is the time of delivery for its
product. This Program Increment (PI), is composed of 5 iterations each of 2 weeks.

Within this level, we have a Product Owner who, using the features in the backlog, determines the tasks
each team must complete. This is done at the start of the PI. For each ART there is a Release Train
Engineer (RTE), who like the Scrum Master monitors the trains progress. These RTEs meet the Scrum
Master bi-weekly to ensure that the objectives are being met. The PI ends with a demo of the integrated
system to check for any problems and reflection to ensure the next PI is smoother.

Within the 5 iterations of the PI, the last iteration is not one for development, rather it is called the
Innovation and Planning iteration. The innovations in this iteration are when the teams plan events like
hackathons etc. The planning phase serves as a point in the PI where the team can reflect on
improvements in the train and plan the next PI.

Value Stream

This is when multiple ARTS must be coordinated together to create a much larger solution that a single
ART cannot create. In this case, we have the same planning, testing and reflecting phases but the people
managing the process change;

Solution Manager: The person dividing the work amongst the ARTs.

Value Stream Manager: Ensures the entire process is smooth and coordinated.

Solution Architect: Ensures that the trains follow the path that is laid out and the overall structure
remains intact .

*********************************************************************************

All SAFe teams are part of one or other Agile Release Train (ART).

SAFe teams are empowered, self-organizing, self-managing, cross-functional teams

Each team is equally responsible for defining, building and testing stories from their Team Backlog in a
fixed-length Iterations

Teams plan and execute two-week time-boxed iterations in accordance with agreed-to Iteration Goals.

Teams will use ScrumXP/Team Kanban routine to deliver high-quality systems to produce a System Demo
on every two weeks.

All different teams in the ART (Agile Release Trains) will create an integrated and tested system.
Stakeholders will evaluate and respond with fast feedback

They apply Built-in Quality practices.

Each ScrumXP team will have 5-9 team members, which includes all the roles necessary to build a quality
incremental value in each Iteration.

ScrumXP roles includes:

Team(Dev+QA)

Scrum Master

Product Owner. Etc..

SAFe divides the development timeline into a set of iterations within a PI (Program Increment).

PI duration is between 8 -12 weeks.

The team will use stories to deliver the value. The Product Owner will have content authority over their
creation and acceptance of the stories.

Stories contain Customer's requirements.

Team Backlog includes user and enabler stories, which are identified during PI planning. When the
Product Management presents the Roadmap, Vision, and Program Backlog.

Identifying, elaborating, prioritizing, scheduling, implementing, testing, and accepting the stories are the
primary requirements of management work in team level.

Each iteration provides:

A valuable increment of new functionality

Accomplish via constantly repeating pattern

Plan the iteration

Commit to some functionality

Execute the iteration by building and testing Stories

Demo the new functionality

Retrospective
Repeat for the next iteration

Teams also support the System Demo at the end of each Iteration. which is the critical integration point
for the ART.

Larger Value Streams will have multiple ARTs.

The Innovation and Planning (IP) Iterations leverage the teams with an opportunity for innovation and
exploration.

*****************************************************************

program level and ART:

In Program level, Value of SAFe is delivered by long-lived Agile Release Trains (ART). Iteration is for team
and train is for the program.

Agile Release Trains (ART) is the primary vehicle for value delivery at the program level. It delivers a value
stream to the organization.

The Program Increments (PIs) duration is of 8 to 12 weeks.

ART is of 5 - 12 Agile Teams (~50 – 125+ people) which includes all the roles and infrastructure needed to
deliver fully tested, working, system-level software.

Each PI is a multiple-Iteration time box. During which a significant, valuable increment of the system is
developed and delivered.

In each PI a "demo" and "Inspect and adapt" sessions will happen, and Planning begins for the next PSI.

You might also like