And again about software testing

There are different point of view on organising a QA chapter. As a QA manager, I see it in the following way. If you ask me ` How  should  QA Chapter look like?` , I would suggest the following structure: Chapter Lead: Person taking final responsibility for decisions Mandatory: 3 QA engineers, 1 BE engineer, 1 FE engineer Optional: Product Owner, Architect, DevOps engineers NOTE: It is very important for me to have representatives of different roles in the chapter, since everyone sees how to improve quality and where to apply improvements differently.  If you ask me ` What  are  QA Chapter  areas of responsibility ?`, I will answer that the agenda of QA Chapter meetings should be based on the following areas: Product quality: Quality of Development Quality of Testing Quality Control Quality of Delivery Visibility of QA work If you ask me ` How are you going to make your QA Chapter performing well?` , I will answer that we will need to define a set of rul...

SCRUM framework has well defined structure, roles and responsibilities. All Quality assurance aspects are distributed between scrum representatives of all levels: Agile Coaches are responsible for quality of agile processes (Quality of processes on company or development department level) Scrum Masters  monitor and help that teams to follow scrum ceremonies and rules and delivery increments in time (Quality of processes on team level) Product Owners are responsible for the product’s value, backlog and prioritisation (Quality of requirements and delivered product) Development team is responsible for quality of delivered increment and development process Developers - design, solution and code quality, QA/Testers - take active part in grooming/refinement sessions to ensure that feature will be tested properly, corresponds to user story acceptance criteria and not bringing issues to the existing product. Perform testing of implemented features and ensure that quality criteria are ...