I was just reading a blogpost from Rick Mans about getting lost being nice for a change ("I like to get lost"). And I think he is completely right. Getting lost opens up new possibilities in many ways.
On the other hand, when talking about testing and Quality assurance, we like not to be lost at all. Knowing where we are and what has to be done in order to reach the ultimate goal; a 100 % tested software product on time and within budget (keep on dreaming).
Tools might help, but there is a glitch...they are expensive and hard to maintain at this moment. But maybe, just maybe, in the near future, they will create tools that are as easy as Google Latitude which let us monitor our progress and update statusses as easy as knowing exactly where we are.
Wouldn't that be nice.....
Subscribe to:
Post Comments (Atom)


I totally agree Reinder. Getting lost can stimulate out of the box thinking, and that I think is exactly what we in our profession need to be doing in order te keep up with the latest insights in software development. For instance in an agile environment you can not rigorously apply the full process of TMap, or all tests in th V-model. You'll need to adapt, re-invent yourself to be able to "go with the agile flow" and still deliver the same accurate verdict on quality as we are used to do. I think you're spot on with that title!
ReplyDelete