SAFe

Question 1

Lack of Scaling Agile

Answer 1

Huge amount of the teams to manage

Lack of Agile understanding on management level

Question 2

SAFe

Answer 2

Scaled Agile Framework:
SAFe is framework for large scale projects and it is a mixture of agile and lean principles

An enterprise scale development framework

a combination of lean and agile principles

*basically its a framework for large scale projects

Question 3

4 levels of SAFe

Answer 3

1. Team Level
2. Program Level
3. Value Stream Level
4. Portfolio Level

Question 4

ART

Answer 4

Agile Release Train:

several agile teams working together to complete a common goal

(5- 125+ people)

Question 5

What are two differences between Scrum and SAFe?

Answer 5

Scrum:
Development Teams are given the freedom to organize themselves and manage their own work
works best when used by companies with a simple organizational structure

SAFe:
requires a high level of coordination and
alignment across teams and management levels which increase work dependency
when large companies want to expand the “agile way of working” beyond the teams

Question 6

Release Train Engineer

ART ROLE

Answer 6

is the chief Scrum master for the train whose job is to facilitate and ensure the ART events and artifacts function correctly

Question 7

Program Management or Manager

ART ROLE

Answer 7

is like the voice of the customer and is responsible for the product backlog and ultimately what gets built

Question 8

System Architect

ART ROLE

Answer 8

defines the overall architecture of the system and helps design the interfaces

Question 9

Business Owners

ART ROLE

Answer 9

are stakeholders of the ART and actively participate in ART events

Question 10

Program Increment (PI)

Answer 10

the ART delivers incremental value in timeboxed periods of 8-12 weeks which typically consist of 5 development iterations and one Innovation and Planning iteration

Question 11

PI Planning

ART Event

Answer 11

• This event is held over 2-4 days and requires preparation, coordination, and communication
• It can be face to face and or virtual
• Each day of the event has its own agenda with issues to be discussed and reworked until their plans have reached a high level of confidence
• A PI planning event is considered successful when it delivers committed PI objectives assigned by the business owners AND a program board which highlights the new feature’s delivery dates, feature dependencies among teams, and milestones

Question 12

The Timing of the System Demo

Answer 12

The system demo takes place as close to the end of the iteration as possible—ideally, the next day.