Comments on: Time of Testing in a System Implementation http://itknowledgeexchange.techtarget.com/itanswers/time-of-testing-in-a-system-implementation/ Wed, 22 May 2013 02:14:48 +0000 hourly 1 By: gabe9527 http://itknowledgeexchange.techtarget.com/itanswers/time-of-testing-in-a-system-implementation/#comment-94423 gabe9527 Wed, 20 Jul 2011 22:36:55 +0000 #comment-94423 There is going to be no hard and fast rules, 4 to 6 months may seem like a long time but when you might be talking about a product that needs to please LEGAL / RETAIL / IT / Compliance teams this is not that long at all.

Design Proving
Proof of concept
User Acceptance testing / Training
Production
LIVE

at any of these times in the life cycle from choosing a product to LIVE the product can be deemed wrong. Some processing may take less time and others will take allot longer. It all depends on the company testing the software and the people involved.

Remember you WILL find faults it is just how effectively you can work out if they are a show stopper or just a change of process. User acceptance and training can take a while or not very long. But train and test to the lowest denominator. This will mean that everyone understands.

Importantly if the product is wrong – try and find out early and stand up and say so before to much time is spent on the wrong product. If it is a product that is going to be created or tweaked for you then expect this to take a bit longer to complete after going live. There will always be something the was missed or not asked for.

I know there are no hard and fast rules I just hope that what I have just typed came across well.

Good luck

]]>