Originally posted by bless 'em all
View Post
Lets say you have 1000 accounts in a salesforce system and you want to change the rep from A to B.
Lets say you build the Account List Primary Key, The Rep Key Before, The Rep Key after.
Lets say you run it through the reporting instance to check
Lets say that as the BI Manager you confirm it's correct.
Lets say you then ask the Administrator to do it ( a simple data change).
Why would you then test it in Dev, then test it in Test where the data doesnt exist, so it's uncheckable, then ask the business to sign it off in dev, then ask the business to sign it off in test, before agreeing a go and no go & getting someone to run it in Production.
IT people get really confused between simple data updates & development change control processes. It's the equivalent of doing an update sql statement. You build the select from to check it, you run it once against a copy of the data, you take a copy of the rows you're planning to change(just in case), then check it worked. You don't have 200 million ******* people checking it, doing 'stories', writing BRDS, discussing it for weeks, test plans etc. It's Business Intelligence not ******* some major ******* deployment for NASA.

IT Developers don't have a ******* clue about data let alone some bint in a back office.

is that I'm a contractor. It's their (the business') data and therefore they should sign off that it's correct, not someone who is an external supplier.
Comment