Skip to content Skip to footer


Don’t implement SAFe in these 5 contexts

If you are on the verge of implementing SAFe OR thinking of implementing SAFe in the near future, HOLD ON! Don’t jump to transformation without enough deep thought.

Agile Principles

Jayaprakash Prabhakar (JP)

Enterprise Agile Coach & SAFe Program Consultant

A seasoned and passionate Agile, Scrum and SAFe® trainer and coach, Jayaprakash Prabhakar (or JP as he is known to all) come with abundant experience of over 23 years in software development, testing, Engineering Leadership, Agile and SAFe coaching. He has helped a few Fortune 100 companies in their Agile / SAFe transformation. He has presented white papers at multiple Agile Conferences

JP sir

By looking at the topic, you must be wondering why I as a SAFe consultant will say “Don’t implement SAFe”. Let me expand the Webinar Topic “Don’t implement SAFe in these contexts…”. Yes, implementing SAFe when it’s not thought through becomes a challenge and, at times, the transformation fails.

Agile transformation is all about 1 team going through the change. However, SAFe transformation impacts a large program that has many teams.

Here are a few contexts where I would recommend not implementing SAFe.

Leadership is not aligned with large transformation
It’s not the right time to implement SAFe
The organization is not ready for the change
The organization is not clear about transformation goals & results
SAFe Framework is not required
The above points look vague to read. In this webinar, I would like to go deep into each of these contexts with different scenarios and industry examples that I have come across during the transformation journey. Looking forward to meeting you, sharing, and learning in this webinar…