Blog

SAFe Is Safe, or how our QA team benefited from scaling the Scrum

Check on the SAFe benefits that our QA team have experienced after adopting the framework.
28 April 2017
Agile
Quality assurance
The article by Vitaly Prus
Head of testing department at a1qa

In the last article of the series, we’d like to cover the benefits our QA consultants experienced after moving from Scrum to the Scaled Agile Framework. Based on our experience of testing software in Scrum and, from now on, in SAFe, we’ll compare the processes and point to the priceless advantages.

From Scrum to SAFe: enhanced speed, collaboration, and predictability

At first, SAFe seemed messy, incomprehensible, and extremely challenging. Mystery of life, so to say. Having no other options but to obey, we got down to work. Days of learning, googling, doing 5 years’ worth of reading up, asking (and answering) questions paid off and in the end we took advantage of the numerous benefits of the new framework.

The most obvious benefits turned out to be the following: synchronized work of all teams and faster delivery of the final product. Let’s have a look at how it was achieved.

To avoid shallow explanations, we’ll use the graphic scheme below. It illustrates the work of the three teams testing software on the project. Scrum is above, SAFe is below.

We hope you remember that for four years almost we were applying Scrum to complete our project goals. As it should be, we organized conventional Scrum events: sprint planning, daily Scrum meetings, sprint review and retrospective.

However, as the number of teams increased, we had to review the entire process and adjust it. It was caused by the customer’s representatives’ desire to participate in all regular events. That’s why we had to defer the sprints start for some days.

This adjustment resulted in the additional week for all teams to finalize all the activities planned for four sprints. Besides, we lacked points of synchronization and didn’t manage to complete end-to-end integration testing and assess the product’s quality before all teams are done.

Only having completed all tests planned for four sprints, we set to the final integration tests and verified the quality of the release product. If it was a minor release, it took us about four weeks to complete integration testing. With the major release, final tests took us about two months.

SAFe helped to change the situation for the better

With SAFe, all teams start and finish sprint activities simultaneously. Synchronization is achieved by the introduction of the intermediate points to sync up (system demo).

Thanks to synchronized work, two weeks of the HIP sprint (check out what HIP stands for here) was quite enough to complete final integration tests. Certainly, if we had to assure quality of the major release, we would allow for more time. Let it be four weeks, it was still two times less than required before.

Put it simply, if sprints started and finished on time and there occurred no obstacles to do the job, the delivery of the shippable product got cut by three weeks.

One last thing

Regardless of scaling, Agile is the same. In large organizations it’s just a matter of making the whole enterprise share the same way of thinking and make everyone feel involved.

SAFe is built in such a way that every person feels valued and invested into the common business. We know the business context, we know the vision of the stakeholders, we collaborate with overseas colleagues and… the Big Picture doesn’t seem to be that messy after all.

Over to you

There are always doubts about the effectiveness of something new. At first, we were thinking that large organization and easy-to-use Scrum don’t mix. After a couple of weeks we made it work on all three levels. We’ve evolved our client’s values and his mindset and managed to keep up our cooperation.

If you are expected to adopt new framework, be it SAFe or anything else beyond your expertise, give it a try! If you give up, a more brave and ambitious service provider will take your place in no time.

Do you have your own tips on how to make SAFe safe, or additions to the article? Please let us know in the comments below.

More Posts

Agile article mini
15 July 2021,
by a1qa
4 min read
How to handle the uncertainty with Agile: three-phase game plan
With the instability taking place even now, we are highlighting 3 steps to address uncertainty issues through Agile and deliver high-quality software.
Agile
12 April 2021,
by a1qa
5 min read
Watch out for 6 telecom trends and QA tips to implement them
In our article, we unleash the upcoming telecom trends and reveal how to be certain in introducing them correctly by applying QA practices.
Agile
Test automation
18 December 2020,
by a1qa
4 min read
Top 5 QA and software testing trends in 2021: responding to a global situation with ease
Rapidly approaching 2021, a1qa proposes to have a closer look at the most influential trends empowering QA teams to perform even more effectively.
Agile
QA trends
Test automation
6 October 2020,
by Dmitry Tishchenko
4 min read
A clear view of smart team scalability
Get to know how to scale your team sagely and gratify end-user needs and fast-paced tech-market requirements.
Agile
Quality assurance
14 September 2020,
by a1qa
4 min read
Winning the competition: how to accelerate time to market
The current global situation has boosted the digital transformation of many processes and operations. Get more information on how to be ahead of competitors by speeding the delivery time.
Agile
Test automation
6 August 2020,
by Elena Yakimova
5 min read
How to arrange fruitful joint work with an outsourcing QA team
The head of the web apps testing department sheds light on how to establish more transparent and effective work on the project cooperating with a remote QA team.
Quality assurance
4 June 2020,
by Vitaly Prus
4 min read
SAFe vs. Scrum, and PI planning essentials
Let's shed some light on the SAFe differences from Scrum that are to be considered by the development and QA teams who have migrated from Scrum.
Agile
Quality assurance
13 May 2020,
by a1qa
4 min read
Understanding Agile testing: 6 questions answered
Consider the aspects regarding the quality of software products developed based on Agile best practices.
Agile
29 April 2020,
by a1qa
4 min read
5 lessons we learned from COVID-19
Here are five key lessons the businesses need to learn during this pandemic to somehow achieve the planned outcomes. 
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.