To STOP the Train - Pull the CHAIN

If you don't do right things at the right time you are inviting failure, as the title goes "To stop the train pull the chain"...you must know when to pull the chain

If you do it in a wrong time, you may end up paying a fine of 500rs maybe(I have never pulled, so I dont know exact amt :))

BUT it doesn't mean you should never pull the chain. Infact you should have the commom sense or presence of mind to pull when it is absolutely necessary

How many times have we said this "we should have done that", "we should have done this" yet we dont do it always...either sometime or rarely

How many times have you pulled the chain in your job? A general myth is the only the Manager or leads are eligible to do this or responsible to do this. I am very sorry for you if you hold this thinking...right from a tester to a qa manager each one of us has responsibility to raise an alarm when something is wrong. It is this inability that causes most harm in projects, people feigning off in guise of their designation or not wanting to be a person who is a whistle blower. we need to make teams aware of the Importance because It matters a lot.

one more analogy comes to my mind

Think of a referee not blowing a whistle when a player make a foul, what if he blows whistle after 5 mins--->he loses credibility, he is embarassed, looses his confidence, his mistake is repeated in all TV channels, "if this mistake is costly"

It is same in our IT projects, if you don't blow the horn at righ time, you are inviting trouble, It may be very costly

what I want to highlight is the Importance of raising alarm at righ time in a project, If its agile then you are bound to be caught for you negligence, BUT if you are not into agile you may escape or it may become a way of life (which may be good for you at that moment but not so good if you happen to join a agile team)

AGILE itself says, search me in a dictonary, you will find "I am deft and active"