Archives June 2021

What are the scaling agile frameworks?

Scaling means making it large, taking it forward to the next level.  Have a look at the agile basics before understanding the scaling agile frameworks. We will divide the framework in 3 categories – (1) Team Level (2) Multiple team level and (3) Enterprise level. Scaling framework is applicable to the last 2 categories – Multiple team and enterprise.

Here is a view of all the agile frameworks across the 3 categories –

Team LevelMultiple Team LevelEnterprise Level
ScrumLeSS (Large-Scale Scrum)  SAFe (Scaled Agile Framework)  
KanbanDA (Disciplined Agile)   
Extreme Programming (XP)SAFe (Scaled Agile Framework)   
 Scrum at Scale 
Note – Spotify is not a model or framework, read the content available on Spotify for your understanding.

What are the various roles in SAFe Framework?

Roles are the backbone for every framework and they help in achieving the planned goals. In SAFe, roles are defined for every configuration. According to SAFe 5.1, configuration makes up the SAFe framework by supporting development & business environments coupled with SAFe Values, Principles, Roles.

There are 4 configuration level in SAFe.

  • Essential SAFe
  • Large Solution SAFe
  • Portfolio SAFe
  • Full SAFe

Below table demonstrates the roles at a configuration level –

Roles in SAFe

Various roles in SAFe

What is SAFe?

SAFe, the world’s most widely used framework for business agility. It is a new way of working that combines attributes of Lean thinking with Agile methodologies to help the world’s largest organizations deliver software and systems to market faster, with higher quality and better-engaged employees. SAFe framework is primarily based on four bodies of knowledge which are (1) Agile (2) Lean (3) Systems Thinking and DevOps. The use of these bodies makes SAFe unique, broad, and scalable.

History of SAFe

Dean Leffingwell and Drew Jemilo released SAFe in 2011. Both of them partnered to roll out the first iteration of the Scaled Agile Framework (SAFe). The idea of SAFe ignited from Dean Leffingwell’s book Agile Software Requirements. This book came up with a framework (Agile Big Picture) that visualized the application of Lean and Agile practices and principles to the Team, Program, and Portfolio Levels. The concepts behind the Agile Big Picture drew from the knowledge pools of Lean, Kanban, Scrum, and Extreme Programming (XP), as well as Don Reinertsen’s The Principles of Product Development Flow.

Core Competencies of SAFe

SAFe is built around 7 core competencies that enable companies to achieve the agility required to handle VUCA associated with customers & technologies.

Lead Agile Leadership
Team and Technical Agility
Agile Product Delivery
Enterprise Solution Delivery
Lean Portfolio Management
Organizational Agility
Continuous Learning Culture

SAFe Principles –

There are 10 Lean Agile principles followed in the SAFe framework

Principle 1 – Take an economic view
Principle 2 – Apply systems thinking
Principle 3 – Assume variability; preserve options
Principle 4 – Build incrementally with fast, integrated learning cycles
Principle 5 – Base milestones on objective evaluation of working systems
Principle 6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths
Principle 7 – Apply cadence, synchronize with cross-domain planning
Principle 8 – Unlock the intrinsic motivation of knowledge workers
Principle 9 – Decentralize decision-making
Principle 10 – Organize around value

SAFe Core Values –

For SAFe effectiveness, the framework focuses on 4 values – (1) Alignment (2) Built-in Quality (3) Transparency, and (4) Program Execution.

Alignment –

One of the key offerings from SAFe is Alignment. This was missing in other frameworks and SAFe included it as one of the values as companies were struggling to put all pieces of the puzzle together. This is one of the reasons why SAFe is quite popular and widely accepted. Alignment starts with strategy and investment decisions made at a portfolio level (call it as top layer), which boils down to Strategic Themes and Portfolio vision. The next level below portfolio is Product and Solution Management. This is the program execution layer (middle layer), Product increment planning (PI) planning coupled with architectural guidance & governance makes the solution technologically sound, robust, and scalable. The bottom layer comprises agile teams (I.e scrum teams, kanban teams) along with the Product Owner who executes the work.
SAFe does not promote a hierarchy approach; the objective of alignment is working toward a common direction.

Built-in Quality –

SAFe promotes the inclusion of quality standards throughout the development lifecycle. Quality is covered in these five aspects – (1) Flow (2) Architecture and Design Quality (3) Code Quality (4) System Quality and (5) Release Quality. This is mandatory for all to follow as quality is one of the key elements in SAFe.


SAFe promotes no secret concept. At all levels ( Portfolio, Program, and team level) there should be transparency which creates trust and openness. Everyone understands the strategy and vision and work towards achieving them in the respective role they play.

Program Execution

This is the binding factor of the remaining 3 values. Agile teams work very well independently however multiple teams do struggle to deliver substantial value, hence focus on execution becomes important.

Conclusion –

One of the most popular framework in today’s world is SAFe. The beauty of SAFe is the revision of the framework based on feedback received from various industries. The 1st version was introduced in 2011 and this has been evolving. More than 70% of the fortune 100 companies have adopted SAFe and counting.

Learn about agile scaling frameworks- What are the agile scaling frameworks?

What is the difference between a Scrum Master and an Agile Coach?

A common question if you are an agile practitioner or new to agile and trying to understand the difference between the top two commonly used roles. Before we discuss in detail the 2 roles, let’s understand the difference between Scrum (What is Scrum) and agile (agile basics). Skip this if you are already familiar with Scrum and agile.

The next aspect is to understand the two roles in detail. Go through this – Who is a Scrum Master and Who is an agile coach.

Let’s deep dive now with these 2 roles –

ParameterAgile CoachScrum Master
Scope of workThis role is spread across various agile frameworksRole is specific to team using Scrum Framework
Role DefinitionAgile coaching is understanding the situation, the values underlying Agile software development, and how the two can combine. Source – Agile CoachingAs a servant leader, a scrum master serves the scrum team, product owner and the organization.
Role – EngagementWorks with multiple teams, various groups & executivesWorks with few teams (not exceed 3)
Role – DurationEngaged with a team for a limited period for a specific goalEngaged with the team throughout
Role -KnowledgeDeep understanding of multiple Agile methodologies.View Understanding of scrum guide is sufficient (scrum ceremonies, scrum events, scrum artifacts.

Summarise –

Scrum Master works closely with the team/s throughout however agile coach is assigned for a certain period/ specific goal with the scrum team. An Agile Coach focus is to increase the performance threshold of the team. Post achievement of the goal, the agile coach moves out from the engagement. Both Scrum Master’s and Agile Coach’s role are different.