Comments on: Handling an Overstructured Mission

By: Jesper L Ottosen

Jesper L Ottosen — Mon, 06 Sep 2010 21:21:30 +0000

Michael & Kristoffer Nordström: You good points are now mentioned on
http://www.eurostarconferences.com/blog/2010/9/6/close-the-tool-and-start-exploring—jesper-ottosen.aspx

By: Kristoffer Nordström

Kristoffer Nordström — Mon, 28 Dec 2009 22:47:22 +0000

I totally agree with your thoughts in the article and think there are far to few organisations that appreciate the skill set that a good tester brings to the table (instead of just being a "click-monkey").

There is however one more activity I would like to add to the process of testing:
"Excellent testing is a process of exploration,discovery, investigation, learning and communicating that information to the stakeholders."

The communication skills of a tester is something that's of vital essence for the tester to be able to be of the most benefit for the project.

By: Matthew

Matthew — Mon, 28 Dec 2009 22:09:57 +0000

Solid Advice, Man. So much of the test literature is about the way the world should be (even the good stuff) – instead of "what we can do when it's not."

Good post, grounded, practical. Thank you.

By: Martin Jansson

Martin Jansson — Sun, 27 Dec 2009 08:48:07 +0000

I've seen similar situation. When I had identified new risk areas and test ideas for the test lead, I was told that the test matrix has been approved already and that there is a set of test cases that should be run before release. So, we were not going to change the test scope no matter what? I think one of the reasons was that earlier that day progress had been reported based on those test cases and management was worried because of lack of progress (on the explicit test cases).

I think progess is tightly connected to this dilemma. Also, how progess is reported today. I am sure management were actually interested in new risk areas and that they expect us to be pragmatic.