EXN QA Internship

Introduction in IT

Belgium Session name: Introduction in IT

Matenstraat 214 (a)
2845 Niel
+32 32 130 383 (t) Main objective: interns get an insight regarding learning and working in an IT company
+32 32 131 454 (f) Secondary objectives:
Romania - interns get an overview regarding the history, vision and projects of Expert Network
Barbu Lautaru 11 (a)
700399 Iasi - interns and the trainer align some secondary objectives / expectations for the internship
+40 332 808 044 (t) - interns learn about different team roles in a project team (pre-requisite for Scrum training)
+40 332 811 504 (f)
- interns get an overview about a day in the life of a tester at EXN
office@expertnetwork.eu
www.expertnetwork.eu
Pre-requisites:
Logistics requirements:
Information sources:

Training time:
Working time:
 page 2 of 2

Get to know each other

Present and future

- company presentation (Q&A)
- internship scope/plan and technical details (Q&A)
- interns expectations & objectives vs EXN expectations & objectives

Expert Network Delivery Model - roles

- Team
- DEV engineer
- QA engineer
- DEV Lead
- QA Lead
- Scrum Master
- Product Owner
- Proxy Product Owner
- Solution Architect
- Delivery Manager
- Business Analyst

What happens in a day as a QA engineer?

- unexpectedly, the QA engineer does not test all the day, every day
- the role of a QA engineer is to make sure that the product that is delivered to the customer meets his requirements - this
is done through specific activities (testing implemented features, looking for defects in the areas where something was
changed, communicating with the client when something is confusing)
- day to day activities: Scrum meetings, writing testcases (mostly at the start of the sprint), testing stories/issues in the
sprint and running testcases, submitting defects and tracking their progress, regression/smoke testing before and after
release, automation
- team roles and the Delivery Model works hand in hand to facilitate better communication inside the organization and
project team, create adaptive processes, bring clarity to the project
- the QA engineer should communicate with the Project lead, Dev lead and Customer to be able to send a clear message
- breaks are important as it clears our minds and make work less stressful (as we are not robots) and activities such as
Darts, FIFA, Ping Pong or just random chatting with colleagues is present.