Is 2 tests per UAT script enough?

Recently a customer asked me if 2 tests per User Acceptance Test (UAT) Script are enough.

This is a good question, UAT testing is key to successful Ivanti HEAT implementations and rollouts of major features/functionality.

How many UAT Tests should be performed per Test Case?

As many as it takes for you and your team to feel comfortable that you can perform your day-to-day job function.

Recommendation and Best Practice is a minimum of 5 tests per UAT Test Script.  Anything less is a risk that the client need to evaluate. Some detailed, complex, and high impact UAT Test Scripts may require at least a dozen of tests for the various scenarios that you have identified. It is better to test more than less, that’s for sure. Perform as many tests as it takes for you and your team to feel comfortable that you can perform your day-to-day job function.

Experience dictates that if UAT (validation of business requirements) isn’t thorough then the likelihood of post-implementation issues, gaps, and problems is much much higher, and can take more time and effort to address than during UAT.   

Intangibles like morale and perception of the new Ivanti HEAT Service Manager system/features can also be negatively impacted.

Also note that you are not bug hunting, so you don’t need to test every single feature and menu item, however you are testing that you can perform your daily job function, so test all the features related to the use case (business process) that apply.

It’s not unlike ordering a fleet of vehicles simply by kicking tires and doing a lap around the parking lot versus more extensive test-drives tailored to the company wide business needs. Sure, everything “might” appear fine, and “might” go fine upon delivery. But those are huge risks to take for a high dollar, high impact, high exposure item that ultimately could lead to work slow down or stoppage.

No matter how detailed your UAT Test Scripts, you need to have a good range of test case scenarios (sample input data) for every test script. Sample input data should be real data, from your existing system, whether it’s a database, excel sheet, or paper forms. For example tickets from your old HEAT Classic system, Paper Forms from a manual system, if you’re going digital, sample rows from an Excel sheet if that’s what you’re replacing. Bottom line, use real data that represents the typical type of data to expect and the UAT Team members can relate to. Tip: Ask yourself if the data could be used for training purposes. If it can, then include it as an artifact for training documentation. If it can’t, then ask yourself if the sample data is a good representation of a typical day in the life of the end user.

The time and effort required is usually negligible. Minutes per test.

A great amount of time and effort has gone into the Ivanti HEAT project, and UAT is a critical milestone in the Software Development Life Cycle (SDLC). So make it count and be thorough on your validation of business requirements, UAT that is.

ivanti-best-practices-a19-consulting-smart-goals-project-tip-latest-solutions-former-Kifinti-consultant

Smart Goals

There is more to Ivanti Service Manager Consulting Projects than software & systems. You need to take a holistic approach and carefully plan your implementation, upgrades, and enhancements. It starts without the software, and requires strategy over tactics. It all starts with goals. S.M.A.R.T. Goals.

ivanti-best-practices-a19-consulting-smart-goals-project-tip-latest-solutions-former-Kifinti-consultant
Ivanti Project Best Practice
More than just IT
  • SMART is an acronym for Specific, Measurable, Attainable, Realistic, and Timebound
  • Goals should be as specific as possible, even if this means breaking them down, by including answers to the popular “W” questions: Who, What, When, Where, Which, Why
  • If a goal is not measurable, it is not possible to know whether a team is making progress toward successful completion. If it’s an Ivanti Project that’s going to take a few months to complete, then set some milestones by considering specific tasks to accomplish.

    A goal needs to be achievable, but at the same time it must not be too easy.
  • A goal that supports or is in alignment with other goals would be considered a relevant goal, focusing on something that makes sense with the broader business goal or Ivanti Project.
  • A time-bound goal is intended to establish a sense of urgency. After all a goal that lacks realistic timing, changes are you’re not going to succeed with your Ivanti Project.

Smart Goal Example

For example, if you’re creating UAT Test Case Scripts, your Smart Goals would be:

  • Specific:
    • Who: UAT Test Lead, designated UAT Team, and Subject Matter Experts (SMEs) as outlined by Roles & Responsibilities Matrix
    • What: Create day to day use case scenarios for job functions for the Ivanti Asset Manager Procurement process
    • When: Over the next two weeks with a Target Date of September 19
    • Where: Go-To Meeting and the Ivanti Breakout Meeting Room
    • Which: Standard Business Operating Procedures with guidance from SMEs and Decision Maker
    • Why: The UAT Test Case Scripts will be used for User Acceptance Testing (UAT) by the broader UAT team to ensure day to day job functions for the Asset Scanning, Procurement Process, Sales Order Life Cycle, Fulfillment, and Invoice Workflow can be carried out with the newly implemented Ivanti Asset Manager system by a19 Consulting.
  • Measurable: Milestones, at least three internal meetings, and breakout sessions for the SMEs for the below categories, with at least 6 test cases that are aligned to the Standard Operating Procedures; Regression Testing, Asset Scanning, Procurement.
  • Achievable: Focus on day-to-day job functions as outlined by the SOPs and seek guidance from SMEs and the decision maker as needed.
  • Relevant: Day to day job functions only as per the SOPs. Do not use the software, this would be system testing, focus is on job functions and satisfying day to day operational tasks.
  • Time-bound: Target Date September 19, with first meeting on September 10, follow up meeting on September 15, and review September 17th.

Remember T.ogether E.veryone A.chives M.ore!