Scaled Agile Framework (SAFe)

Giriş

Yazıya başlamadan önce içimden "Yet Another Process Framework" demek geliyor. Youtube nasıl "Useless Marshall Arts" videoları ile doluysa bu framework te benim gözümde aynı.

Neyse : ) Yine de notlarımızı alalım. 

Mission Driven Development yöntemi SAFe'ten daha hafif olduğunu iddia ediyor

SAFe Nedir?

Açıklaması şöyle. Yani çevik prensiplerin (agile principles) büyük şirketlerde daha fazla ölçeklenerek (scale up) tüm kurum seviyesinde kullanılmasını amaçlıyor.

SAFe is a framework that explains an approach for scaling agile for working in larger enterprises and bigger teams, working on the same or multiple products.

Tarihçesi

Açıklaması şöyle. 

SAFe was first developed in the field and was elaborated in Dean Leffingwell's books and blog. Version 1.0 is the first official release in 2011. 

Aslında kısa bir geçmişi olmasına rağmen hızlı bir şekilde güncellenerek sürüm atlamış. Ben bu yazıyı yazarken 5. sürüme gelmişler. Açıklaması şöyle

Starting at its first release in 2011 already five major versions have been released[10] while the latest edition, version 5.0, was released in January 2020.

Safe Konfigürasyon Türleri

Bunlar şöyle

- Essential SAFe

- Large Solution SAFe

- Portfolio SAFe

- Full SAFe

Agile Release Train (ART)

Konfigürasyon Türlerini anlamadan önce ART'yi anlamak gerekir. Açıklaması şöyle.  Tüm tüm takımların aynı anda başlaması ve aynı anda release vermesi anlamına geliyor.

Synchronizing deliverables

Agile frameworks are designed to enable the development team to be autonomous and free to design how they work. SAFe acknowledges that, at the scale of many tens or hundreds of development teams, it becomes increasingly chaotic for teams to fully self-organize.It therefore puts some constraints on this, so that where teams are working on the same product, their deliverables can be better synchronized for releasing together, although this has been one area in which SAFe has been criticized.

Roller Nelerdir?

Agile Release Train, Program seviyesinde düşünülüyor. Bu seviye için de 3 tane rol düşünülmüş. Açıklaması şöyle. Bu roller Product Manager, System Architect ve Release Train Engineer

SAFe collects small product teams (often Scrum teams) into “Agile Release Trains” — groups of teams with an additional layer of management roles spanning each group at what is called the “Program level”.

Generally these roles impede the autonomy of teams. They add process and communication overhead out of proportion with the value they provide.

These roles include a Product Manager (PM), a System Architect (SA), and a Release Train Engineer (RTE).

Bir başka açıklama şöyle

What Are the Different Roles in a SAFe Framework? 

SAFe Scrum Master (SSM)

You might know that a traditional Scrum Master concentrates on the basics of a team-level Scrum. In contrast, when it comes to the SAFe Scrum Master, he is entitled to look into the intricacies of the entire organization and then strategize and execute around the Program Increment. 

SAFe Product Owner (POPM)

The SAFe Product Owner is a multi-tasker responsible for budgeting, defining the priorities, and determining the workflow.  

SAFe Advanced Scrum Master

The Advanced Scrum Master with Scaled agile framework is a senior to the SAFe Scrum Master. He is responsible for assisting in interactions with the product management team, architects, and other project stakeholders at the enterprise level.  

SAFe Agilist (SA)

An Agilist is a lean-thinking manager who introduces and implements the principles and values of the Lean-Agile Mindset. The Scaled agile framework agilist is primarily responsible for creating and leading efficient teams throughout the agile framework implementation roadmap.

Release Train Engineer (RTE) 

The Release Train Engineer is another essential individual responsible for applying their Lean-Agile knowledge to deliver the final product value. 

Product Manager Ne Yapar

Açıklaması şöyle.

The SA and PM define and break up larger pieces of work (often inherited from the portfolio process above) and then pass the pieces into the teams.

Release Train Engineer Ne Yapar

Açıklaması şöyle.

Release Train Engineers define consistent cross-team process and cadence, and handle many operational tasks. 

Large Solution SAFe Konfigürasyonu

Açıklaması şöyle. Yani program seviyesinden de büyük bir süreç

...groups of groups of teams with analogous roles to those at the program level, but spanning Release Trains.

Allowing time for innovation

Sanırım SAFe'teki tek hoşuma giden şey bu. 1 hafta (veya artık ne kadarsa) öğrenme için vakit ayrılması. Açıklaması şöyle.

The SAFe planning cycle recommends including an additional iteration after a release, so that teams can improve their practices and are ready for the next planning increment. 

SAFe Agile Değil Eleştirisi

SAFe bürokratik, fazlasıyla karmaşık, planlamaya fazla önem veriyor ve değer katan şeyleri değil, planları öne çıkarıyor eleştirileri var. 

Ancak bence asıl önemli şey, SAFe'in kullanmayı düşündüğü diğer çevik süreçleri de bozduğu eleştirisi

Takımların kendini organize eden (self organizing), bağımsız (autonomous) ekipler yerine, yukarıdan yönetilen ekipleri öne çıkarıyor eleştirisi zaten en vurucu nokta.