Skip to main content

What is a good Agile Tester ?

Its a good question!

Over the last couple of weeks I have read various articles highlighting what a good Agile tester is… all very good, but all very different!

"Testers are responsible for quality" No, no, no...

So the question is, what do YOU think a good Agile Tester looks like?

Here are my thoughts:

I strongly believe that a good Agile Tester is whatever it needs to be for a given project. Everybody within an Agile team has the same goal and requires continuous collaboration to succeed.

At the start of a sprint, an outsider looking in, should they be able to pick out who is the Developer, BA or Tester? I don’t think so. Everybody needs to be involved in defining things such as processes, user stories and acceptance criteria etc.

We all need to deliver value, we all need to continually look for improvements and we all need the ability to respond to change.

It’s only at this point that I see people doing specifics to their specific role, and for testers believe our main purpose would be:

·       Provide continuous feedback
·       To be creative
·       Think about the end user
·       Validate that all acceptance criteria has been met
·       Ensure that no testing has been overlooked
·       Continuous learning (Keep up to date with new tools & approaches)
·       Provide the business with confidence in the feature under test


Having the right tester mind set and an easy to work with personality is always a winner for me J

This is just a few thoughts, Hope it helps.

Comments

Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:


As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

Leeds Testing Atelier - April 2018

The Importance of Building a Good Community of Practice

Within every organisation i think we can all agree that 'collaboration' is a major factor to the success of any project or initiative.

As organisations grow, new teams are created and existing teams fragment from each other, this is natural and i doubt that will change.

So what impact does that have to an organisation?
Stress in the work place? Unmet expectations? Relationship breakdown? Low Morale? Dissatisfied Clients? Collateral damage is inevitable.
When clients are dissatisfied, they often take their business elsewhere, which costs your company money. Poor communication can lead to high employee turnover, which creates a cost of hiring and training for new positions. At the least, with lower productivity and an unclear sense of purpose, poor communication causes employers to pay for work hours that are not efficiently spent, costing money, affecting efficiency, and keeping employees from reaching their true potential.
Its sometimes difficult to work on projects where you/y…