How to Reprogram a Mindset before Accepting Agile Principles?

by Nataliia Vasylyna | June 7, 2016 12:40 pm

Prior to plunging into Agile, a software testing company should forget a bunch of rules typical for traditional practices.

What Traditional Principles Should Be Unlearned?

• Before its execution and completion, the testing process needs to be thoroughly planned and designed. Why to unlearn: In Agile, the process of testing is not divided into phases. Instead, it is continuous. That’s why the testing stages often intersect.
• Testing can only be performed according to test plan and test strategy. Why to unlearn: Carefully arranged release plan usually covers the activities that need to be done. At the same time, having an overall test strategy is also a good idea for Agile.
• QA teams should work independently from development teams. Why to unlearn: An Agile team comprises both a team of developers and a team of testers. All team members work on the same goal – to create a product of a high quality.
• The more defects are reported, the better the efficiency of a testing team. Why to unlearn: Agile is not about putting quantity over quality. A testing team should not just report a bunch of minor cosmetic bugs but also share the responsibility for the overall quality of a product.
• The principles of automated testing[1] should be applied only during regression testing[2]. Why to unlearn: Automation is an essential part of Agile, and it helps a lot to develop a better product. Automated test scripts can be created and executed during multiple different types of testing.

A majority of companies already tried this approach and experienced that Agile makes software testing, website testing and mobile testing[3] much easier.

Related Posts:

• Assessing Success of Agile Project[4]
• Agile Testing Top 10 Practices: How to Improve Release Management?[5]
• Agile or Not: Tips to Determine a Team’s Approach to Product Development[6]

Source URL: https://blog.qatestlab.com/2016/06/07/accepting-agile-principles/

---