SAFe – Scaled Agile Framework overview


SAFe – Scaled Agile Framework overview


SAFe, or the Scaled Agile Framework is a comprehensive tool to adopt lean-agile efficency in larger scale. The framework is typically aimed for orginazations with multiple teams that work on the same product or service.

SAFe adopts well known methods and practices and provide a context where they will create synnergies, and a faster and more structured approach to aligning teams internally and externally.

In SAFe there a four specific core values and some practices that are critical for success.

Alignement in the entire orginization. It is critical that strategy desicions, business objectives and initiatives are aligned all the way to the development teams and finally the receivers of the product itself. If we can’t have this alignement, how can we expect the teams to align their efforts?

A constant attention to code quality. If the development teams doesnt focus on code quality practices (like XP) their technical dept and delays will effect their sourronding teams.

Transparency on all levels is neccesary to buuild trust. From the very idea to the very release of a finished product increment, everything must be visible.

Program execution is essential. The Agile Release Train must depart as planned, every time. We can not be transparent and aligned if we aren’t certain who is delivering when. Do not ever stop the train.

Together with these practices there are some other things that are needed to sustain a scaled working structure.

Common release planning – or Program Increment planning. We need to sit down together and plan as a whole team on how we will execute the next Program Increment. To evaluate all dependencies and create trust internally between all stakeholders, we need to look eachother in the eyes. This typically takes two days every three months, but are well worth it.

Sprint alignement between the development teams must be withheld. It doesn’t help anyone if we cannot perform at one unit. Say that one team runs three week sprints and the others two weeks sprints. The common planning wil introduce delays which is a major cost when we are working on the same product.

We all need a common language. We must use objectives, and evaluate these business objectives to ensure that all teams work towards the same goal, and speak the same language as the receivers of the finilized product.

SAFe-3.0-Thumbnail-200pxThere are many other aspects to scaling that needs to be considered, but it would be too much text for you guys who are just visiting our website.

We recomment that you click on the icon to get to the Scaled Agile Framework webpage to educate yourself further. And book a meeting where we can discuss pros & cons of going SAFe.

SAFe-badge-bronze-smallCoreAgile is very happy and proud to present all our knowledge to you in a meeting or a 1 hour SAFe foundations presentation on your request.

 

We have appended a shot video from “The agile Samurai” that will give you a 5 minute overview on what the framework is all about. Enjoy!