Sprint 4: What’s the non-technical skill that every tester should have, but most don’t seem to?


(Heather) #1

In Dominic’s absence, kicking off Sprint 4 Sprint planning for Sprint 4

Kicking off today 2018-06-13 finishing 2018-06-27.

Looking forward to your answers on this one. Perhaps you might like to look around the Club for some inspiration :wink:


(Tracy) #2

Ability to write a comprehensive bug report or testing notes.

What I mean by that: I’ve know a lot of testers who stay brain-immersed in their testing to the extent that while writing up notes or a bug report, they forget to include proper context. Some of the 'where/how/when/with what" information is perfectly clear to them, because they are soaking in the application at the time. But if that output spurs questions a month or two later… it’s no longer clear what happened.


(Paul) #3

The ability to communicate clearly with all roles and levels of an organisation - from senior management and CIO level to the sales staff and people on the support desk.


(Paul) #4

Also - and this may or may not be considered a technical skill - with machine learning becoming more important in tech in general, I believe that testers with a strong (at least undergraduate level) background in maths and statistics will have a real and distinct advantage.


(Lee) #5

This is a tough one as I imagine I’m not alone thinking there are multiple answers to give. This is a prompt I can definitely work with though :slight_smile:


(Melissa) #6

Speaking and writing skills. Presentation skills. Leadership skills - and I don’t mean managerial, I mean the kind that let you get your point across without going red-in-the-face. If someone had started me off with those kinds of leadership skills, I’d be miles ahead in my career for sure. There is also the case that one can only learn those with time… but it would have been nice to be mentored into it.


(Kim) #7

Agree, that’s why retros are a great place for the team to work together, assisting ones who have an issue getting their bug or note writing clear enough for anyone to understand


(Ady) #8

Empathy. For users, for team mates, for yourself


(nicola) #9

How to talk about their testing and what they h ave done in daily stand-up so that others actually know what they’re doing (not just “testing”)


(Lee) #10

I would probably say tenacity. The ability to articulate their point well and stand their ground if they feel the need to defend their viewpoint.

Unfortunately sometimes allowing yourself to not be easily manipulated is important when testing software (especially when faced with strong bias!).


(Kris) #11

Similar to a few other comments; I find in more junior QAs it is the “fear” of talking to more senior members of the team (PO, SDM, Dev) about a valid bug they have found. They have the fear as they don’t think their bug will be taken seriously or that they will look down on the them for finding the bug. However I always tell the junior QA just to do it - get all the evidence you can to prove it is a bug, triple check, and then if you really need to approach someone more senior team member just do it…you can’t not be confident with triple checked facts, and anyway, if you’re wrong it’s your job to find bugs.


(Adam) #12

Understanding how to argue properly (i.e. from a solid factual basis), and how to counter fallacious arguments. Going back to the previous sprint’s topic of useful books, Carl Sagan’s “A Candle in the Darkness” has excellent coverage of the types of false arguments.


(Silvia) #13

The ability to find the balance between having self-confidence (to defend the defects they find) and putting themselves on developers’ shoes (to not hurt them when they talk about the errors)


(Shivani) #14

The ability to realise that the scope of tester’s responsibility is way beyond releasing product. Keeping eyes on logs, monitoring also comes in their plate.