Moving things live into production is when IT has the most impact upon a business. The customers may experience a downtime, their workflow maybe changing, or many other situations. It is also the time that truly determines if the change meets the customers requirements. Or is it?
One practicality that may be implemented before moving a change into production is the completion of user acceptance testing. Then there is the actually signing of the user acceptance of the project or request. This should be done by both the requestor, and honestly the authorizer also. The requestor is the individual who made the request for work, and the authorizer approved the work to be completed. This way everyone involved in requesting the change is involved. And ideally the specs of the change are met before it is implemented into product.
That’s a better mechanism, than implementing and finding out...
"oh, it functions that way?"
Subscribe and Share!
Did you enjoy this article? Your feedback is very important! I'd like to invite you to keep up to date with the latest posts from Anticlue. We offer several venues. If you have some questions, help can be found here.- Become a Facebook Fan
- Subscribe to Anticlue
- Follow me on Twitter
- Add to Technorati Favorites
- Digg this post
0 Comments to “User Acceptance”
Please share your thoughts and suggestions
-
Receive Our eNewsletter
-
About Me
Welcome to the Healthcare IT Project Management Blog of Elyse Nielsen. This is the place where I share the ideas I have learned, the things I’d like to remember, and my thoughts for a brighter future. Find out more.
Subscribe to Our Tips
This weblog is licensed under a Creative Commons License.