Get certified - Transform your world of work today

Close

QA Approaches in Agile

19 February 2016

Alhad Akole
Zensar Technologies Ltd


Testing roles in the Agile world are not new. Still, assuming cross-functional teams don’t exist, which is possible in given scenarios, test engineers have to do many tasks and play different roles at different times.

This is my list of ideas and practical cases that I have found useful for the QA member to consider:
  1. Understand that “a fool with a tool is still a fool.”
  2. Prevent (QA) defects rather than try to them (QC).
  3. A mindset change is required for Agile testing.
  4. Understand the Agile Manifesto.
  5. Understand the Agile Testing Manifesto.
  6. Understand the Agile Testing Pyramid.
 
Agile-Testing-Triangle.jpg
The Agile Test Pyramid
 
  1. Break the Manual Testing Paradigm.
  2. Understand the Agile Testing Quadrants.
  3. Look for opportunities to push more and more automation tests toward the bottom of the Agile Test Pyramid.
  4. Move from manual testing to automated testing.
  5. Understand the big picture.
  6. Learn to read code that has been developed by developers.
  7. Learn to collaborate more with the BA, developers, UI/UX, the PO, and end users to understand the real needs.
  8. In sprint planning meetings, discuss all possible test scenarios for the user story.
  9. Look for NFRs (nonfunctional requirements, aka “-ility” test scenarios).
  10. Actively formulate the DOD for the testing.
  11. Identify high-level risks and test strategies.
  12. Log defects, if really required, in the defect management tool; collaborate more with developers to fix defects.
  13. Use more and more exploratory testing.
  14. Don’t hesitate to test the functionalities on development environments to ensure that quality code comes to the QA environment.
  15. Look for regression packs to remove technical debt in testing – look back to regression test packs and remove unwanted test cases that might be useful in the current state of the project.
  16. Automate all phases of testing, right from test data creation to having regression testing based on the nature of the project.
    1. “For every nail there’s a hammer” – look for right kind of tool.
  17. Only running tested features are important.
  18. Involve business users in testing activities early on.
    1. If they are not part of the testing activities, it’s kind of risky and a sign of mini-Waterfall in Agile, as teams will wait for acceptance for releases/phases to complete.
  19. Enable continuous integration.
  20. Enable continuous builds.
  21. Always understand and speak the business language during interactions with the PO.
  22. Wear different hats during Agile projects: PO, UX/UI, end user, developer, DevOps, etc.
The future is all coding, so learn to code – automate!

 

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.



Article Rating

Current rating: 4.6 (5 ratings)

Comments

Be the first to add a comment...


You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.

 

Newsletter Sign-Up

Subscribe