SAfe overview
Blog

How our QA team scaled Agile: SAFe overview

Read how our QA team had to replace Scrum principles with those of SAFe and how we managed to achieve win-win results.
17 March 2017
Agile
Quality assurance
Article by Vitaly Prus
Head of testing department at a1qa

Read how our QA team had to replace Scrum principles with those of SAFe (Scaled Agile Framework) upon the customer’s requests and how we managed to achieve win-win results.

The a1qa acquaintance with SAFe started two years ago. A customer, who has been cooperating with us in QA outsourcing for more than 4 years, confronted us with the fact: “As of today, we start working with SAFe, guys.”

However, we had no other options but to obey. We learned the basics, read numerous hands-on articles and started tuning our processes. Looking ahead, we must admit that we did it quite successfully.

To date, we’ve been working with SAFe for almost two years. And our experience is what we want to share. Hopefully, we’ll foretell some of the difficulties that your QA team may come across.

Let’s start with some basics.

When apply SAFe?

Google displayed us the following big picture:

Agile: SAFe methodology

The core thesis about SAFe is that it contains a number of rules and regulations to ensure smooth agile scaling in a large number of development teams.

  • Are there multiple software products developed and roles in the project?
  • Do you need dozens of approvals to put in place any new suggestion?
  • Are there many development teams who are eager to apply the lean-agile approach?

If the answers are “yes” than SAFe is what can be of help.

What are the levels in SAFe?

SAFe basic structure contains three or four levels depending on the specific needs of the company. They are portfolio, program and team levels. The 4.0 SAFe that has arrived this January has introduced the fourth optional level, called the Value Stream that should be applied in companies with over 120 people working on heavy software systems. In teams of 50-125 people (as it was in our case) the three-level structure is more convenient.

To gain a better understanding of every level, let’s take an example of the project and focus on its levels. It’s important to note that the levels will be analyzed from the QA team’s point of view, not the business one.

Let’s imagine that we have to enhance the e-commerce application aimed at selling books. The current functionality of the app is very simple: the customer uses the search bar to find the book he or she needs and orders it. When the book arrives at the warehouse, manager notifies the customer and he/she collects it from the warehouse. Apparently, the app is too simple to be competitive on the market. We need to strengthen it adding some more features that will make it more attractive.

The portfolio level is the highest level of concern in SAFe. The responsibility of the portfolio level is to discover major initiatives (business epics) that would reflect business priorities. Epics can be functional and architectural by nature.

As for our website, the functional epics shall be the following:

  1. Organize delivery across the country with the opportunity to follow order processing in a user’s account.
  2. Develop an online communication platform for books amateurs.

Architecture epics should be the following:

  1. Integration with GIS (geographic information system).
  2. System migration to the cloud.
Example of SAFe number one

So far it’s pretty easy, we hope. Now we are going down to the program level.

Program level is where business epics are split into features and development team and other resources work on the implementation of the features. A feature is a part of the product that should give some flow of value to the customer or to business.

Let’s split one of the epics on the team’s level. Online communication platform epic can be subdivided into the following features: user’s account, forum, and private messages.

Example of SAFe number two

On the team level, every feature shall be reformulated into clear and short user stories that can be estimated and implemented within a sprint.

For instance, private messages feature can be broken down into the following user stories: send messages and get messages and save chat history options. Architecture epics have to be broken down as well.

Example of SAFe number three

In such a manner, with every next level, the tasks get smaller in size and their boarder lines are specified. Estimation also gets more accurate.

In the next article, you’ll learn the workflow specifics on each of the SAFe levels.

More Posts

QA for financial applications: 4 reasons why it is a must-have
17 November 2024,
by a1qa
5 min read
QA for financial applications: 5 reasons why it is a must-have
Striving to release high-quality financial apps? Read on and discover 5 core reasons why your eBanking and financial solutions need software testing.
QA consulting
Quality assurance
Test automation
Why do bugs get missed
27 September 2024,
by a1qa
7 min read
Why do bugs get missed? Learn the problems and tips to avoid them
Still, finding overlooked bugs after the app goes live? Let’s find out why this happens and how to fix it.
Performance testing
QA consulting
Quality assurance
Test automation
Soft skills 101
13 September 2024,
by a1qa
4 min read
Soft skills 101: how to supercharge business success in 2025
Discover the value of soft skills for both career development and workplace improvement and learn some tips to sharpen them.
General
Quality assurance
QA to ensure smooth migration to the cloud
15 August 2024,
by a1qa
3 min read
QA to ensure smooth migration to the cloud
Learn how effectively migrate to the cloud by implementing QA activities.
Functional testing
General
Migration testing
Performance testing
Quality assurance
Test automation
Load testing
23 July 2024,
by a1qa
3 min read
7 reasons why businesses need load testing 
Want to optimize software performance or ensure its smooth functioning during peak sales season? Discover how load testing may help.
Quality assurance
Test automation
27 June 2024,
by a1qa
3 min read
Establishing seamless interaction between development and QA teams to boost productivity
Establishing seamless interaction between development and QA teams to boost productivity
Agile
General
Quality assurance
Test automation
17 June 2024,
by a1qa
5 min read
Shifting to test automation to maximize software quality
Explore in the article why businesses should move from manual testing to test automation.
Quality assurance
Test automation
RPA in QA
28 May 2024,
by a1qa
4 min read
Embracing robotic process automation to drive efficiency in QA
Discover how the convergence of robotic process automation helps reshape software testing practices.
General
Quality assurance
Test automation
QA for fintech
7 May 2024,
by a1qa
5 min read
Navigating the fintech frontier in 2024: QA’s role in delivering high-quality financial software 
Unveil the future of fintech innovations and learn to refine their quality with the help of software testing.
Blockchain app testing
Cybersecurity testing
Quality assurance

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.