There are 4 different levels of SAFe in 4.0 version onwards.

They are shown in the figure below:

• Team Level-:

This level is the same as that of what we know about Scrum, it’s Artifacts, roles and events/ceremonies.

All scrum teams are part of one or the other ART (AGILE Release train).

ART is explained in the below diagram. Basically, this is a team of 50-100 PEOPLE (cross-functional) responsible for defining and deploying the new system, plan, commit and delivers the solution to the customer in a particular time frame.

• Program Level:

At this level product and program manager has the authority to define the Backlog.

At this level, different roles are DevOps, System Architect, RTE, Product Management, System Team, Business owners, Customer, UX Architect.

The main events of this level are:

• ART:

1. This level value of SAFe is delivered by ART. Iteration is for the Team and train is for the program. It delivers a value stream to the organization.
2. SAFe artifact hierarchy is Epics->FEATURES->user stories. User Stories then drill down to the team level.
3. Various team (from marketing, development, quality, operations, and deployment) forms 'Release Management Team'. They will approve routine releases of quality solutions to customers
   

• PI planning- 

Duration is about 8-12 WEEKS. A very huge event where all the cross-functional team members across the globe participate and work towards the common goal. A valuable increment of the system is developed and delivered.

PI deliverables:

• System Demos-At the end of each PI (Every 2 weeks) the full integrated work of all teams is demoed. This is in addition to each team iteration demo. Stakeholders provide the feedback and corrective action needs to be taken if required.
• Inspect and Adapt- This is also held at the end of each PI to demonstrate the solution, get the feedback, solve the problem and identify improvement areas
• Architectural Runway- It is an EXISTING code base, components, technical infrastructure on top where new features are developed without much change in code.
• Release Any Time- This separates the development cadence from the solution release cycle. Trains may release whatever is needed at any time.
• Value Stream Level-This level is optional but required in below cases.
• The organization is big in size

1. Complex solutions
2. The solution requires multiple ART’s
3. System challenges

• Portfolio Level-

Highest level of concern/involvement in SAFe is portfolio Level.

1. It provides basic budgeting and other governance mechanisms.
2. This way it assures that investment in the value streams provides the basic returns for the enterprise.
3. Portfolio Program Management are key stakeholders and they are responsible for delivering the business results.
4. Here the backlog contains the EPICS (Which contains many features.), EPIC owners are responsible for driving this.
5. The main roles involved are Enterprise Architect, PPM (Program Portfolio Management), Epic owners.
6. Events are Strategic business planning and Epic planning.