I really oppose Big Bang implementations unless there is absolutely, no other option - i.e. for "real" reasons like the power station example sited in the article. Normally you end up with a big bang because the business won't pay for a dual running period or there is some arbitrary deadline.
Every big bang implementation I've seen has involved lots of last minute frantic fire fighting in live.
It often for silly reasons too, e.g. an infrastructure difference between test and live no one noticed or the user "forgot" about that monthly report they always do when signing off their requirements..
I have also seen a worrying trend for "MVP" testing where I work now. We recently put a major new customer facing system live, and while we thankfully didn't do a big bang we did an "MVP" performance test (under protest) which didn't really prove anything. Funnily enough said new system is performing like a dog in live, time to get the fire extinguisher out...
Biting the hand that feeds IT
