This website is now archived. While it is fully functioning, I no longer maintain it and comments are turned off on most posts. Please visit the updated

Business is Religion

I usually refuse to get drawn into debates about religion and, even more so, despise to tell people my views. I’m not ashamed of my religion, it’s just I feel that people may think I’m trying to convert them – I don’t want to come across as ‘preachy’. People should make up their own mind regarding their beliefs… who am I to question them? Today, I’m going to make an exception.

I recently learnt that someone who I know believes in Creationism: they believe that Carbon Dating is unsound and that Darwin was incorrect about the Origin of Species. Evolution is not how humans have come to be, and the Earth is between 6 and 10 thousand years old – not 4.5 billion as some claim. To believe otherwise is heresy. (N.B. A 2006 poll in this country showed that only 48% of respondents believed the origin of life to be evolutionary – 22% chose Creationism, 17% Intelligent Design and the remaining 13% ‘did not know’. [Ref: 1 | 2])

This person I know is a Christian – not strictly devout, but still committed to the religion and its teachings. Does Creationism really have to go hand-in-hand with a serious belief in religion?

To me the Bible is a non-factual text – to be taken with a pinch of salt. It is a series of teachings collected together in one book. Not represented as fact, but rather as a series of moral stories to mull over; to consider and live your life according to their teachings. After all, the Bible was written by humans – fallible humans. It surely can’t be taken as fact for that reason alone?

In IT, Creationism is the belief that a large, new project can be completely specified and then successfully developed by a team… in one go. As anyone who has worked in application development will know, this is unfounded and not based in reality – developing a successful application arises through evolutionary methods. Constant interaction is required between analyst, developer and user in order to fulfil a requirement. Multiple versions are required to create a successful, working application as desired by the end-user. The first attempt will almost always be incorrect.

The analyst’s Use Case document is not to be taken as fact. Developer input is required so that their specialist skills and technical knowledge is applied during development. The user’s requirements may change and the document must reflect this. The document develops – evolves – just as the application does.

Although, this doesn’t fit with management’s view of how a project must be completed: it must be created perfectly, first time round – further versions are uneconomic and costly. So, the facts are ignored in order to appease those who we perceive as above us.

Religion is Politics? Business is Religion.