Blog

Introducing QA to Agile team

Introducing a QA team into a software development lifecycle (SDLC) usually starts with an initial knowledge transfer phase that may take from a week up to a couple of months.
18 October 2013
Agile
The article by Svetlana Pravdina
CEO

Introducing QA consultants into a software development lifecycle (SDLC) usually starts with an initial knowledge transfer phase that may take from a week up to a couple of months. By default, knowledge transfer phase duration depends on two significant factors:

  1. Development phase. QA team that starts working simultaneously with the development team requires less effort to get on board in comparison with the latest project phases when the requirements are partly outdated due to changes in technical decisions or business priorities.
  2. Project and domain/area complexity. Providing QA for typical end-users’ products (e.g., social networks or shop sites) doesn’t require a long period of team adaptation in comparison with complex business solutions.

However, there is another factor to consider – process adaptation. I’d like to cover this aspect based on the Agile environment (Scrum in particular). According to a1qa experience with more than 100 projects completed using Scrum, there are three significant issues each team faces:

1. Development team has never worked with QA professionals before

Scrum suggests that Agile teams should be cross-functional. And most of the development teams try to follow this rule when establishing Agile techniques.

After a while they encounter two major problems:

  • Developers are not good enough in software testing and miss obvious defects or spend too much time on the task
  • Developers are demotivated by doing the job they are not interested in.

Having a cross-functional team has its own benefits, and the most considerable is a feeling of responsibility.

However, imagine that you need cardio surgery. At a hospital, they say it will be performed by a dentist explaining that their team is 100% cross-functional. Would you take this risk?

For most companies, the only solution is to introduce a professional QA team. In most cases, it will affect the established process familiar to everyone, e.g., defect management should be introduced together with other QA activities that are often neglected in cross-functional teams.

To avoid misunderstandings and conflicts, a QA team should be eager to introduce changes and reason them.

a1qa also advises to set up training sessions for development and management to give an understanding when, why, and for sure, how QA works. Regular (informal) Q&A by quality assurance sessions are a very popular way to get a development team involved in what QA engineers are doing.

And of course, a QA team should become a part of a project team doing Sprint plannings, Scrum meetings, and retrospectives accepting responsibility for team success or failure.

Work in Agile team

2. Development or QA team has no experience working Agile

Agile is called so for its flexibility in rules and regulations. Scrum is usually considered to be easy to adopt and follow, especially considering other methodologies like RUP.

At the same time, to be effective in Agile, the team should spend at least 2-3 full Sprints to get accustomed to the speed and process, understand the best practices, feel the team responsibility, and get used to each other.

The most effective Agile teams are those that have been working with no staff changes for 3+ months. During this timeframe, a team will go through some successful and unacceptable Sprints, define their own velocity, get more familiar with estimates and risks based on their team experience.

A good practice is to have at least 50% of the team members who have been working in Agile before. They may give a hand to newcomers, share knowledge and expertise.

a1qa tries to balance Agile teams starting with at least 75% of Scrum gurus and keeping teams unchanged for 6 months and more. We also do an introductory training in Scrum for all crew members who are joining a1qa team as well as for development teams.

3. Communication aspect. Another default rule in Scrum is team co-location

The world is changing introducing globalization into everything (and cloud computing is a good sample for IT). Communication is still a very important part of the Scrum team. Normally, Scrum meetings should be held in one room, where everyone should stand up and provide their update to the crew.

For distributed teams, we use the same approach but different tools – the team has daily Scrum meetings using Skype, GoToMeeting, or Polycom. Therefore, while the tools change, the process itself stays the same.

To cut a long story short, involving the QA team in an Agile process is challenging. Nevertheless, consider the benefits you get: high-quality products, happy customers, time to market reduction, costs optimization, and effective developers.

More Posts

Enhancing Agile and DevOps processes
28 February 2024,
by a1qa
4 min read
4 actionable tips to enhance Agile and DevOps processes 
Streamlining Agile and DevOps workflows? Learn practical recommendations on how to achieve this.
Agile
General
Test automation
Navigating the future: QA trends that will define 2024. Part 1
15 January 2024,
by a1qa
4 min read
Navigating the future: QA trends that will define 2024. Part 1
Discover topical software testing trends that will shape 2024 and empower companies to smoothly implement advanced technologies.
Agile
QA trends
Quality assurance
Test automation
agile-qa
30 November 2022,
by Dileep Marway
3 min read
Agile QA – what is needed for greater flexibility and speed?
What should your QA team focus on to become truly agile, enable quality at speed, and contribute to lasting performance improvement? In addition to introducing test automation, I suggest considering shared responsibility for software soundness.
Agile
Quality assurance
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation
Test automation in Agile
20 May 2022,
by Alina Karachun
5 min read
Test automation in Agile and DevOps: Maximizing flexibility and speed
Global market tendencies and user behavior are changing rapidly, if not talking about the software itself. Familiar situation? Find out how to get ahead of the curve with test automation in Agile and DevOps.
Agile
Test automation
Agile and DevOps in eCommerce QA_mini
30 September 2021,
by Alina Karachun
5 min read
Agile and DevOps: Boosting the quality of eCommerce apps
What benefits do Agile and DevOps bring to eCommerce business, and how QA helps with that? Find it out in the article.
Agile
Quality assurance
Agile article mini
15 July 2021,
by Alina Karachun
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

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.