Skip to main content

Testing is not a phase

I got to listen to a discussion today where a topic was if a team kanban board should have a "ready for testing" column.

I am happy that the discussion ended with the decision not to have it.

I am happy on that because in the world of software development, testing is not a phase to happen somewhere after programming and before pushing something to production. 

If/as testing is about raising good questions, seeking answers to those questions, and about exploring risks and opportunities - it should happen all the time. From the beginning when thinking if the thing should be built at all, into the end when analysing and observing the actual impacts.

Everything that happens between is about doing, and any extra column, phase and handover you create inside this is going to hurt you.


Popular posts from this blog

Should testers learn to automate? is the wrong question

Should all testers learn to automate? Or shift left? Or shift right? Are the wrong questions. The correct question is, should everyone in the team do what is in the long run the most valuable thing to do for the good of the team & product & customers.  The answer to that question is Yes. This is the question you should be pondering, when thinking about what and how to do stuff.  This is the question you should be pondering, when thinking what you are best at, and how you can best help the team.  Forget your role. Forget the hype.  Instead ask yourself, what should I do now that will in the long run provide most value to the team & product & customers. Then (learn to) do that. And you are going to do great. Now, and in the future.