When should QA be conducted in Scrum?

Discussions
,
1

I am a QA engineer on a product development team at a Japanese company :jp:.
In our team, QA is only conducted during regression testing before a release.

However, we often find critical bugs during regression tests, which disrupts the smooth progress towards the release.
I would greatly appreciate it if you could share any best practices from your experience or methods for incorporating QA during the sprint :man_bowing:.

2 Likes
2

Test the idea (requirement testing)

Test the early builds (sanity / survey testing)

Test the stable builds (exploratory testing)

Tests using Regression

When not testing, prepare test data, checklists, test ideas, etc.

6 Likes
3

I’m a tester in a sprint team and participate at every meeting. Similar to what @parwalrahul shows.
Don’t let you tell by anyone you can not be there. My coworkers find my input very helpful and it can get on the same page as the developers early on.

3 Likes
4

What do you mean when? Always! At all stages of software development

4 Likes
5

Thank you for taking the time to answer so promptly!
I appreciate your guidance on sanity testing, as it was new to my team.

Based on your advice, I learned that there are various approaches, and I’m eager to introduce these practices to my team to ensure we release a high-quality product.

1 Like
6

I’m grateful for your prompt reply.
Your advice is extremely helpful.

In our sprint team, we often have “development consultations,” but I haven’t been participating in them.
Moving forward, I will actively join these discussions and make an effort to catch up on information quickly and provide feedback.

I’m very glad to receive advice that I don’t often hear in Japanese development culture!
This has renewed my motivation to work hard starting tomorrow.

4 Likes