![](bg8.png)
tionnaire; (ii) sample representativeness and size; (iii)
understanding of roles by the team. To minimize (i),
the questionnaire used was based on the Competency
Mapping Model already established in the (Salda
˜
na-
Ramos et al., 2012) literature. As for (ii), because it
is a study conducted in a single software development
team, limiting the variety of roles to only 3 managers
and 22 members of the testing team, this study was
limited to only one context. And in (iii) we asked
the participants which role was closest to their main
attributions, they answered according to their percep-
tions, which can generate a bias of interpretation or
understanding of their own responsibilities. A map-
ping of the roles was carried out in relation to the po-
sitions, roles, and time of experience. A divergence
was perceived in terms of experience level and the
role answered by the participant. Therefore, the role
declared by the participant was considered.
6 CONCLUSIONS
This work presented the analysis of the competencies
levels of a testing team in an R&D Company from the
perspective of managers and team members regard-
ing all the roles involved in the testing process. As a
result, we noticed that the professionals believe they
have more competencies than those needed to carry
out their activities. Some general competencies the
participants already meet the manager’s expectation.
This research contributes to the industry by establish-
ing the competency levels expected by contractors
and comparing them with the professional’s results,
which facilitates interviews, career planning, and in-
vestment in training. For the academy, it’s important
to develop the themes that need to be improved dur-
ing graduation, forming professionals who are better
prepared for the job market. As future work, we high-
light the need to apply the framework in larger teams,
with a greater variety of roles, in addition to consid-
ering a better refinement when assigning a role to the
participant, which corresponds to their position. In
addition, it is important to carry out a study of how
these skills can be developed, given that professionals
need to meet the expectations of managers, in addi-
tion to complying with the demands of the projects.
ACKNOWLEDGEMENTS
This research was supported by Eldorado Re-
search Institute and Federal University of Ama-
zonas (UFAM), CAPES - Financing Code 001,
CNPq process 314174/2020-6, FAPEAM process
062.00150/2020, and grant #2020/05191-2 S
˜
ao Paulo
Research Foundation (FAPESP). We also thank the
USES research group for their support and practition-
ers for their voluntary participation in the study.
REFERENCES
Abran, A. et al. (2004). Swebok. Guide to the Software
Engineering Body of Knowledge.
Ahmed, F., Capretz, L. F., Bouktif, S., and Campbell, P.
(2015). Soft skills and software development: A re-
flection from the software industry. arXiv preprint
arXiv:1507.06873.
Ardis, M., Fairley, D., Hilburn, T., Nidiffer, K., Towhidne-
jad, M., Willshire, M., et al. (2014). The software en-
gineering competency model (swecom). IEEE Com-
puter Society, Los Alamitos, CA.
Assyne, N., Ghanbari, H., and Pulkkinen, M. (2021). The
state of research on software engineering competen-
cies: A systematic mapping study. Journal of Systems
and Software, page 111183.
Faria, A. C. C. and de Castro Filho, C. M. (2014). Profis-
sional da informac¸
˜
ao: estudo dos egressos no estado
de s
˜
ao paulo, mundo do trabalho, habilidades e com-
pet
ˆ
encias. PontodeAcesso, 8(3):44–63.
Holtkamp, P., Jokinen, J. P., and Pawlowski, J. M. (2015).
Soft competency requirements in requirements engi-
neering, software design, implementation, and testing.
Journal of Systems and Software, 101:136–146.
ISTQB (2022). International software testing qualifications
board. Accessed: 2022-07.
Kaner, C., Bach, J., and Pettichord, B. (2011). Lessons
Learned in Software Testing: A Context-Driven Ap-
proach. John Wiley & Sons.
Llorens-Garcia, A., Llinas-Audet, X., and Sabate, F. (2009).
Professional and interpersonal skills for ict specialists.
IT professional, 11(6):23–30.
Maia, N., Oran, A., and Gadelha, B. (2023). Comple-
mentary material - Analyzing the competencies of test
teams.
Pressman, R. S. and Maxim, B. R. (2021). Engenharia de
software-9. McGraw Hill Brasil.
Salda
˜
na-Ramos, J., Sanz-Esteban, A., Garc
´
ıa-Guzm
´
an, J.,
and Amescua, A. (2012). Design of a competence
model for testing teams. IET Software, 6(5):405–415.
van Veenendaal, E., Garousi, V., and Felderer, M. (2022).
Motivations for and benefits of adopting the test ma-
turity model integration (tmmi). In International Con-
ference on Software Quality, pages 13–19. Springer.
Vroon, M., Broekman, B., Koomen, T., and van der Aalst,
L. (2013). TMap next: for result-driven testing. Uit-
geverij kleine Uil.
Expectation vs Reality: Analyzing the Competencies of Software Testing Teams
159