Quote:
|
Originally Posted by JPnyc
Testing should always be done first. I would then implement in as small a 1st bite as you can. There are ALWAYS some unforeseen problems.
|
I agree with you when it comes to applications that just aid employees do something they were already doing. What if the new application implemented is changing the way users are doing their job?
Take as an example companies that have implemented an ERP system and had to change a lot of the way in which they operated to adjust to the ERP system. How can you test such a system that changes the way things work? It's difficult to ask a part of a department to do things the old way and another part to try the new way.