Best Practice Tip – UAT Action Plan

One of the most crucial steps in System Development Life Cycle (SDLC) is User Acceptance Testing (UAT), a type of system and business objective validation, performed by the end users, and business objective sign off by the project owner; not to be confused with System Testing which is performed by the Ivanti Developer and/or ISM Administrator

Many Ivanti Service Manager implementations fall short when it comes to proper UAT Testing, be it due to a lack of resources, time, or budget, but more often than not due to a shortcoming of proper UAT Action Plan and UAT Test Cases and Scripts.

Today we will focus on a sample high level UAT Action plan:

• Refresh UAT with PROD (ISM Administrator)
• Push Asset Scanner Packages to UAT (ISM Consultant)
• Create UAT Test Cases/Scripts (ISM Administrator/Knowledge Manager; with assistance from ISM Consultant)
• Create Documentation for ISM Users (ISM Administrator/Knowledge Manager with assistance from ISM Consultant)
• Test Data Preparation (ISM Administrator)
• Test Run (ISM Administrator)
• UAT Run (ISM Administrator+ Storage Managers)
• Remediation (ISM Consultant)*
• UAT Run (ISM Administrator+ Storage Managers)*
  • Including Validation of Documentation and Knowledge Article Creation (ISM Administrator/Knowledge Manager)  
• Confirm Business Objectives – Sign Off (Project Owner)
• Schedule Push to PROD (ISM Consultant)
• Communication Plan (Core Team)
  • ISM Change Control Announcement
  • ISM Change Control Email with Documentation
    • Determine schedule
      • Before – for example 3 days before
      • At PROD Push
      • After – optional – follow up 
• PROD Push (ISM Consultant)
• Validate PROD Push (Core Team)
• PROD Emergency Support – 1 to 2 hours after push – (ISM Consultant)