Categories
Best Practices Ivanti

Implementation Milestones

Over the last 2+ decades implementing HEAT IT Service Management and Ivanti Service & Asset Manager, the following implementation milestones, aka rollout milestones, or roadmap have been deeply ingrained and proven to be the ultimate success factor and project structure.

From Scope of Work to Go-Live (Rollout) there are many steps that need to be carefully planned, communicated, and enforced.

Categories
Best Practices Ivanti Service Manager

ITxM Health Check Audit

ANNOUNCING

THE HANDS-ON, ROLL-UP YOUR SLEEVES,
LET’S GET-TO-WORK, HERE IS HOW-YOU-DO-IT,
TAKE YOUR IVANTI SERVICE MANAGER IMPLEMENTATION
TO THE NEXT-LEVEL

ITxM HEALTH CHECK AUDIT

The purpose of this intense 60 minute ITxM Health Check Audit is to review your current Ivanti Service Manager (HEAT ITSM, ISM) and/or Ivanti Asset Manager (IAM, ITAM) system and processes to provide you with a Road Map to ITxM Excellence

During the ITxM Health Check Audit you will learn how to:

  • Provide massive value with Ivanti Service Manager
  • Get extraordinary results from your Ivanti System
  • Decrease your support calls and emails
  • New and easy best practices for your Ivanti Implementation
  • Advanced workflows to streamline your Ivanti systems and processes
  • Cut your Ivanti ISM Project costs in half and double your return
  • Take your Ivanti Service Manager Implementation to the next level!
  • Plus… many more ideas, concepts, systems, and strategies

Success with Ivanti Service Manager is not a mystery…
It’s a SYSTEM!

See what others have to say:

“EXP had completed an Implementation of the Ivanti Service Manager and Asset Manager toolset. The implementation team from Kifinti Solutions were helpful in getting it up and running, but we needed someone that could take EXP to the next level and configure the tool so we could utilize all of its potential, with the latest solutions and Ivanti Best Practices. As EXP was also in a transition period where our processes and workflows were being redefined, Gregor and a19 Consulting were able to work with us to align our working processes with the workflows within the Ivanti Service Manager tool.”

— Steven Morin | EXP | Helpdesk Manager

Former Kifinti Solutions Consultant - gregor@kifinti.com now focusing on a19 consulting Best Practices and Ivanti Professional Services

Give me just 60 minutes of your time and
I GUARANTEE I will improve your Ivanti Implementation!

Gregor Anton | a19 Consulting

Only $159.00 USD

Why is it so inexpensive?

We are an independent consulting company going back to 1996 with HEAT IT Service Management and Ivanti Service Manager and have developed best practices systems for Ivanti Business Partners and Fortune 500 Clients for over 2 decades. This session acts as an ‘acid test’ for your company. A truly distinctive experience and one that can only be appreciated first hand.

Categories
Best Practices

Best Practices: File Naming Convention

An often overlooked best practice is that for file naming conventions, albeit not an Ivanti Service Manager Best Practice, it certainly is a best practice you should consider for your Ivanti Service Manager and Ivanti Asset Manager Projects.

Files should always be renamed with a prefix of the last modified date in YYYY-MM-DD format, for sorting purposes, and contain a meaningful name and version number.

The file name itself should be meaningful to the subject matter and topic at hand, for example if you’re working on UAT Test Scripts for Ivanti Service Manager then you could use 2020-05-19 HEAT ISM – UAT Test Scripts as the complete file name. Leading Date, Subject Mater, and Topic.

Descriptions such as “final” and “complete” should also be discouraged as 99% of the time there will be revisions.

This best practice ensures files are easily found, sorted, and clearly indicate the last modified date, version, and file contents.   

Note that the file saved date/time often changes as files are sent via email, download again, copied, or saved by mistake.

For example, Task #8043 has two attachments and without proper file naming conventions it is unclear which file is the latest for the Ivanti Service Manager UAT Test scripts:

  1. Copy of 2020-09-11 – Sample UAT Test Scripts Complete.xls
    should be
    2020-09-11 HEAT ISM – UAT Test Scripts v2
  2. 2020-09-11 – Sample UAT Test Scripts Complete.xls
    should be
    2020-09-14 HET ISM – UAT Test Scripts v3

In Summary, for file naming conventions use the format YYYY-MM-DD Subject Matter – Topic – v#.

Categories
Best Practices SDLC UAT

What is UAT Testing?

  • The purpose of User Acceptance Testing (UAT) is to test use cases, that is specific day-to-day operations in the life of an end-user and their required tasks to perform their job function
  • UAT Testing differs from System Testing in that System Testing is focused on software functionality.   UAT Testing is focused on job function, that is day to day operations can be performed.  Therefor access to Ivanti Service Manager (powered by HEAT) is not needed to build UAT Test cases, in fact it is discouraged to use HEAT as your focus should be on building use cases about day to day operations, operating procedures, such as Logging an Incident, searching for customers, assigning 2nd level support, and so on.
ivanti best practices regression testing user acceptance testing uat ivanti service manager ivanti asset manager a19 consulting ivanti professional services best practice systems
  • Regression testing refers to testing of existing functionality to ensure that recent changes do not adversely affect existing features.  For example, when implementing Asset Management, the existing Incident functionality is tested to test use cases such as creating an incident, creating a task, updating incidents, closing tasks, incidents, etc. In addition to UAT Test Scripts, you will want to do a comparison of existing workspaces, existing functionality, and existing features, to ensure existing functionality has not been impacted.

If you’re looking for sample UAT Test Scripts, be sure to contact us!

Categories
Best Practices Ivanti Ivanti Project

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!

Categories
Asset Scanning Best Practices Ivanti Asset Manager Ivanti Service Manager

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)

If you’re looking for sample ISM UAT Test Cases and Scripts from the a19 Consulting – Ivanti Best Practice System then be sure to contact us!