It takes two to three minutes to find out if you have Knowledge Tester in your team or not. Here are some conversations from my own experience:
“how’s the project going?”
“good, we shipped a build to client last week.”
“that’s great. What’s the client name?”
“umm…aaaa… I don’t remember exactly”
Well, this guy is definitely not a knowledgeable one. Need to put on a learning path
(photo from openclipart.org)
“your project name is XYZ support, right?”
“no, it’s actually YXZ support”
“Oh Ok, so is this YXZ the company in US that works on yxz stuff”
“well, I’m not sure what YXZ stands for”
Better than the previous one, but still don’t know the domain much
“your project name is?”
“it is ABC support. ABC is a file format of our competitor’s product LMN and we want to export that data as one of our file formats and then import into our database”
“that’s great. Thanks”
See the difference and now imagine what levels this tester will go.
“so you are the only tester on the project?”
“no, there are 2 more, one in our East Europe team and other… ummm… perhaps in US”
“ok, what’s the name of colleague in East Europe?”
“it is … well, I don’t remember right now”
Seems like this tester is always sleepy on the status update calls and have no clue who the other tester is and what that tester is up to.
“how many defects are pending for the release?”
“I have 15 defects assigned to me and not sure how much is the total count”
See how narrow is the view window of this tester and chances are less that it will contribute for the team goals.
“who is your project’s product owner… John?”
“well, product owner is in fact Dave who is talking to the client. John is acting as Scrum Master to get the work done. And then we have Amy working from the Test Management side to look for release readiness”
So this tester is in picture of what’s going on in the project and who runs the show.
Did you have conversation with the tester in your team that sound similar? I’ll love to hear those.