Team structure and composition - NextensArelB/SwaggerGenerationTool GitHub Wiki
##How Test Automation Team works Test Automation Team is working agile and has its own backlog. There is a 6 week sprint, starting on a Wednesday. Every Tuesday there is a weekly standup in which the status and progress of the tasks in the sprint backlog is being discussed. The planned tasks have deliverables and progress can be measured like any other development project team. Deliverables of our TA Team can be code, Wiki documents or delivering sevices to other teams. Before a task will be closed it will be either reviewed by the members of the test Automation Team themselves or it is validated by the members of the Test Automation Guild.
##Work in the individual teams
Next to the "normal" test work that is performed when preparing for an release or testing an feature we want to have in each sprint of the teams an user story that will be "test automation" related to make the running of the test automated in the CICD pipeline or to increase the test coverage or refactor to a new test framework. This way we are closing the test automation gaps that exists in the teams.
##The Test Automation Team consists of:
PO processes - Monica Homma PO technology - Ben van Tol DM - Monica Homma See link for description of responsibilities of PO and DM.
Automation lead: Richard Engeringh (20%) Quality Engineering lead: Clint Velberg (30%)
Automation engineer support area BC: Richard Engeringh (20%) Automation engineer support area Naslag: Yogeshwari Muthusamy/Arel Bokobza (20%) Automation engineer support area Fiscal: Martijn van der Zalm (20%) See link for Automation engineer support
6 weeks sprint, with: Weekly standup and refinement Objective: discuss status, progress and outcome of the sprint board tasks How: 30 min for status and progress and 30 min for refinement and content In case of large or complex deliverables which are too big to discuss in the weekly meeting, a separate meeting will be organized. Who: members of the Test Automation Team When: every Tuesday from 1530-1630
Sprint retro and planning Objective retro: discuss the to improve and to keep Objective planning: discuss and agree on the sprint planning of the coming sprint Who: members of the Test Automation Team When: every 1st Wednesday of the sprint from 1500-1600