As technology has evolved and become more user friendly recently, users' adoption of an functionality has become a more important topic. This is something I addressed recently in a blog post about the Solution Manager Expert article "Configure EEM to Monitor Your End Users' Application Issues," but it also applies to our latest article about user acceptance testing.
As Allison Flexer, a vice president and senior change manager, notes in her article "Functional Suggestions for the Coordination of ChaRM User Acceptance Testing," it's important to test user acceptance when rolling out the Change Request Management functionality of SAP Solition Manager.
The objectives of a user acceptance test (UAT) are to ensure that all the business requirements have been met, that the system works as designed and that it provides consistent and dependable business value in a production environment. Completion of UAT instills confidence in your end-user community that the solution will work as planned.
She goes on to explain the roles and scenarios of a UAT along with providing a sample spreadsheet you could use to trac
For a series of UAT prerequisite tests you should perform at minimum -- and this can change depending on the complexity of your system -- see the table below.
Solution Manager Expert subscribers can read the full article here. For more information about subscribing, go here.