I have been reading this book named '6 thinking hats' by Edward de Bono since last 2 days. Book says every individual can think under 6 hats or 6 categories. And this kind of thinking results in efficient usage of time and helps in a better decision making. Blue hat is the moderator hat. It will guide the thought flow process. White hat deals with facts and figures. It has no emotions attached. Wearing a green hat signifies the thinking is diverted for fresh ideas. Yellow hat signifies the thoughts which concentrates on positive aspects associated with a decision. When an individual wears the Red hat he/ she thinks with a higher emotional quotient. When someone is said to wear a Black hat on a topic that implies the individual will be cautious and will emphasize on the negative aspects.
I found this black hat very interesting and to my surprise Edward de Bono thanked only the Black Hat in his acknowledgement. My interest in the black hat is due to the kind of thinking a user switches to, when he wears this hat.User takes a stance of critic, thoughts are now concentrated on the negative aspects. The user becomes a devil's advocate.
My interest in the black hat is also due to the fact that, this is the hat which a software tester is proud and anxious to wear. While reviewing the requirement documents, while writing the test cases and so on. Because it is in our blood… to be cautious, not just being cautious but extra cautious.
This is the attitude which a tester should have order to nurture and deliver a better application or product.
But the black hat needs to be removed at once when we are talking to developer regarding a defect. We wear a white hat; show him the impact or severity of the defect. Talk in figures and facts. While we are discussing a CR or a suggestion which needs to be implemented; we wear a yellow hat.
At this point I questioned myself: Why can't a developer put a black hat while testing and then a yellow or green hat while coding? The answer is: No one will criticize oneself when:
1. one 'believes' that he is right and what he is doing is 'acceptable' (acceptable as per the requirement and design document).
2. one cannot see the broader view and overall affect when he is dealing with a smaller portion. ('Module-based' development)
Don't forget to wear the black hat next time you test!!
Testing on the Toilet: Cleanly Create Test Data
4 hours ago