{"id":1101,"date":"2014-02-11T10:48:24","date_gmt":"2014-02-11T18:48:24","guid":{"rendered":"http:\/\/www.testing4success.com\/t4sblog\/?p=1101"},"modified":"2023-07-30T11:47:03","modified_gmt":"2023-07-30T18:47:03","slug":"agile-agile-and-one-more-time-agile","status":"publish","type":"post","link":"https:\/\/www.testing4success.com\/t4sblog\/agile-agile-and-one-more-time-agile\/","title":{"rendered":"Agile, Agile and one more time Agile!"},"content":{"rendered":"

What should everyone working in Agile environment realize when in the process of developing product? And particularly what role plays QA in the Scrum.<\/p>\n

Why Agile? It is simply keeping everyone in team on track to deliver quality product in the set time-frame. Flexibility is the primary characteristic of this method. It is so nice not to have to change routine, but reality check says that we have to be flexible. There are so many benefits from having this quality. Let\u2019s talk about it.<\/p>\n

Agile software development<\/b> is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen tight interactions throughout the development cycle. (Wikipedia)<\/p>\n

In a nutshell – having this dynamic method implemented in the process of developing software lets teams stay focused on delivering the product while responding and adapting to business changes throughout the process. As a result of practicing Agile methodology during production the associated risks were effectively reduced and the software systems have much better addressed the business and customer needs.<\/p>\n

Thereafter, everyone who involved in the project including QA needs to adapt to this style of workflow and mindset in order to achieve better results. Let\u2019s see how Agile and Quality Assurance really fit together.<\/p>\n

Traditionally, QA role was only involved at the end of the project once all coding was complete. Typically, QA would be given a requirements document against which they wrote and executed test cases. However, in Agile QA\u2019s responsibilities go further beyond just executing test cases and reporting bugs.<\/p>\n

Agile Quality Assurance involves the whole team. They bridge the gap between users and developers. Quality Assurance should be fluid and agile themselves, focusing on techniques to optimizing a new strategy to testing. Everyone is responsible for quality. Team collaboration can best understand and discuss new requirements,<\/p>\n

The following facts show how the QA role carrying through agile testing:<\/p>\n