I was once asked which is better? A watch that won’t run or a watch that always shows the wrong time. The former is better because at least twice a day it would be showing the right time if you did look at it then!
People in a manufacturing setup at least know their domain very well. What is IT domain? Straight off I can hear, project management, SCM, developing, testing etc. I will drawl and agree. However if we believe IT is only an enabler then it is important to know how business problems can be addressed using IT.
Are we doing the right thing by way of learning domain? My preliminary talks with various people indicates it is not so. Either I have been talking to the wrong set of people or I am sadly right. As a developer usually we are constrained by a use case and we stick to the minutiae of the letter in the document and miss the business world. As a business analyst our only focus is to clarify and communicate to the extent required no further. As a tester we are bound by the test case and no more.
A car company’s forecasting model for their cars cannot show fractional cars. This is obvious and simple. However when it was pointed out the defending argument was “well the use case does not specify that”. Right take the use case writer over red-hot coals, but hey what were you doing?
Remember 16/64 gives the right answer by knocking of the common digit 6. Logical yes. Correct? No. (BTW there is another example of similar nature).
In the end what you take with you is the business aspects of the work. Do the right thing by domain. Unlike the manufacturing counterpart you have an opportunity to learn more than one domain. Today it is airlines, tomorrow could be healthcare. Are you still not convinced?