Do I need to be afraid if my team is moving to Agile?

Joel Montvelisky, Chief solution architect at PractiTest – test management tool, and Rob Lambert, Director of cultivated management, a tech consulting company with today’s topic: Do I need to be afraid if my team is moving to agile?


  • You shouldn’t be afraid when your team is moving to agile, nobody expects you to become a developer. With that said, don’t consider yourself non-technical as testing is technical work even when coding is not required from the tester.
  • Even though it will be better for you to evolve as a tester and embrace the technical side, there are many things you can provide to the team from a non-technical aspect. Most important, customer advocacy, the ability to see above the technical layers and dictate if a use case makes sense from a user perspective. Secondly, guide your team through the correct testing process.
  • Who does the actual testing work is less relevant, as long as you can dictate the essence of the tests and their purpose in relation to the development of the software? Even if the developers in your team are in charge of writing the actual test cases, you can be the one directing them in the right direction.

How can you learn to be more technical?

  • Stay curious. If you hear some technical terms you are not familiar with, it will be a good idea to write them down and try and understand those terms. The first step for being technical is to want to know how the things you are testing is pieced together, and slowly increase your technical knowledge by staying curious.
  • Pair as often as you can with a developer or a technical tester, you can learn a lot by staying curious and observing them.
  • You need to understand what is the best way for you to learn. Learning by observing is great but it’s not for everyone. If you know you learn better by reading a book or watching a video on youtube, online course or any other source, and practice by yourself don’t be afraid to do so.
  • In testing, there are two different approaches, active testing, and passive testing. In Active testing you press the buttons, it can be conducting exploratory testing, scripted testing and more. In Passive testing, you work with log files in order to investigate sources of issues. Passive testing can be very beneficial for a tester.
  • Use tools that help you understand user environments from behind the screens such as Google Analytics, New Relic, Fidler, and more, as it can guide you in your testing process and make you more technical.
  • If you are going to work in production, try to be a part of, and lead the process of monitoring. You are not going to be able to test everything before a release and therefore some of your testing processes will be done by your users, but this process still needs to be monitored.  
No comments yet.

Leave a Reply