Agile Testers - To Be Or Not To Be Independent?

Recently I’ve been having discussions with various people on the ‘independent software testing services’ of a QA team/people in an organisation. Some have said there’s no way this can occur in a team using agile methodologies; others have said it’s essential to maintaining an effective and objective department devoted to improving product and process quality.
My view? It depends on the definition :-)
When it comes to asking whether a tester who is involved in a fully functioning scrum team, who is working daily with developers to define acceptance criteria (yes, I believe everyone should have a say), collaborating on test environment construction, investigating broken builds and similar complex tasks, are they 100% independent and flying the flag for the QA dept? I’d have to say no.

What they’re doing, and I believe it’s what they should be doing, is working with the team to build the best possible feature in that sprint.
If that’s the case, when is a tester working as an independent consultant for the test automation services cause then? Well, confusingly enough, at the same time. Whilst they’re knee deep in code and environments and repository failures, the tester needs to still keep their QA hat on and think of the bigger picture. There has to be someone in the team tasked with ensure quality assurance is being thought of and has a voice throughout the sprint.

This might take the form of reminding everyone to document their unit tests, double-check with the product owner on a specific piece of functionality and broadcast the findings, point out that code coverage has fallen for testing (be that for any type), whatever. They must remain focused on ensuring the best quality code is produced and is exactly what the product owner wants. And this requires an independent mindset to achieve it.
So the life of an agile tester is a complicated one. They have to be independent whilst not, involved up their neck in code but also standing back and observing the team’s productivity, and ensuring that there is adherence to the quality processes in place. A tough call indeed, and one that I think should merit huge salaries to compensate

Comments

  1. Debra J FosterNovember 15, 2019 at 2:00 AM

    Thanks for your great information

    Looking for top software testing companies in USA? On the off chance that software needs to be useful for use, it needs to finish different arrangements of the QA assessments. DataWider has curated this list of software testing companies after broad research dependent on their client reviews, quality, loyalty, flexibility and capacity.

    ReplyDelete

Post a Comment

Popular posts from this blog

How can product quality improvement be tracked from sprint to sprint?

I’m interested in defining the best metrics to use for checking whether the product quality is improving as time, and sprints, pass by. One obvious factor is the number of automated tests passing in the continuous integration builds related to the coverage of functions in the code. Or is it? Do the tests literally show the product quality? What if the finished article isn’t what the customer wanted? There are then a suite of tests making sure that the software does something it’s not meant to. Number of defects? Measured against what? The list of possibilities goes on, what I’d like to find out are tried and tested measurables. Does anyone have a list they use in every project? Update by Kenny 08/11/09 :- Ok, I’ll try and answer my own question here (the power of reflection!). There are two scenarios in projects which require different solutions in relation to metrics gathering. They are :- 1) A project run using mature agile methodologies from day 1 2) A project which ...
Read more

Agile v Waterfall - Which Is The More Risky?

I still find it strange that companies unfamiliar with Agile automatically view it as being a methodology that pays no heed to process or ensuring quality of output. From my experience the quality is actually a lot better, the timescales set are achieved more readily and everyone involved has a much greater understanding of the product and its development status at any one time. At present I´m working on a project where I´ve had to split the test team into two due to several companies working to build a complex product together. One team is performing agile QA in a sprint team, the other is working ´the old way´. It´s very interesting to note that all the worry and uncertainty is coming from the team working with the traditional model due to the fact that timeframes having been guesstimated months ago about environments, data and functionality that no-one knew about then. As time marches on we appear to be spending more time in meetings discussing what we once thought was go...
Read more

Details, Fiction and Software testing services

  No matter what DevOps processes, models and applications corporations use, testing is a vital Component of the general DevOps procedure — don't just to be sure code alterations work as envisioned and integrate well — but to make sure the necessity improvements do break the performance.” – How DevOps Transformed Software Testing Whether or not your web site is still in improvement or out inside the wild, we are able to get the job done with any surroundings. Our testers can collaborate along with your developers and task administrators, and in some cases be part of your Jira, Slack, and standup calls. Find out more about our Site testing services. For that reason, the workforce has to analyse the code on the continual foundation to keep the code foundation in a great maintainable state. This will protect against uncovered complex debts, process crashes and highly-priced fixes.” – Sergey Terekhov, Defining and monitoring the code top quality Most of these tests are more expens...
Read more