ivanti-best-practices-SDLC-software-development-life-cycle-a19-consulting-ivanti-professional-services-best-practice-systems

Which Software Development Life Cycle (SDLC) do you follow for your Ivanti HEAT Neurons Implementation Projects?

Back in the HEAT for Windows days the only SDLC methodologies that were on the HEAT radar and considered “the norm” were Waterfall and Iterative, and there was little to no discussion about SDLC.

In 2001 Agile entered the stage Lean followed soon thereafter in 2003, and in 2008 DevOps entered the stage. Depending on who you ask, the majority of software development is still Agile, some Lean, and DevOps is the latest contender.

Meanwhile, HEAT for ITSM emerged, was acquired by Ivanti, rebranded Ivanti Service Manager, and again rebranded to Ivanti Neurons for ITSM as part of another practice, the Shift-Left Methodology.

SDLC History

Iterative 1950s

Waterfall 1970

Spiral 1986

Agile 2001

Lean 2003

DevOps 2008

ivanti implementation packages - former kifinti solutions consultant -best-practices-heat-ivanti-service-manager-ism-itsm-itam-ivanti asset manager

Typical Ivanti Implementation Timeframe

This question came in through my Podcast Question/Topic Form from Andre in Frankfurt, Germany as well as Adrian from Melbourne, Australia.

This question came in through my Podcast Question/Topic Form from Andre in Frankfurt, Germany. What is the typical Ivanti Implementation Timeframe? Ivanti Service Manager (HEAT ISM) Implementations really vary based on business requirements.  There is no quick silver bullet or cookie-cutter Scope of Work, and Estimates can vary greatly between Ivanti Business Partners, and independent consultants. Be sure to listen to what I have to say and my unique insights thanks to 25+ years of Ivanti Service Manager (HEAT) experience. podcast.a19consulting.com

What is the typical Ivanti Implementation Timeframe?

Andre, Ivanti ITSM Project Manager, Frankfurt Germany

Ivanti Service Manager (HEAT ISM) Implementations really vary based on business requirements. There is no quick silver bullet or cookie-cutter Scope of Work, although unfortunately Ivanti and Business Partners, use templates across the board for clients with different needs and business requirements. Worse yet, I see quite a bit of overselling with no clear Implementation roadmap or plan, and far too many implementations go off track due to poor execution, delivery, or budget exhaustion on what was sold as a slam dunk and clearly isn’t.

Implementation Considerations

First and foremost you will want to do a self-assessment of which ITIL processes (Incident, Change, Service Requests, Problem) are a must-have or nice-to-have and build a time-lined roadmap. As well you want to review top obstacles and challenges, see my Ivanti Implementation Poll to see what area of focus resonate.

Once you have established a high-level roadmap you will want to work with a seasoned Ivanti Service Manager Consultant to solidify a scope of work and provide you with estimated effort.

Estimated Effort

Estimates can vary greatly between Ivanti Business Partners, and independent consultants. One factor is the overhead that Ivanti Business Partners have and the guaranteed referrals that Ivanti Business Partners get from Ivanti, and their associated price tag. Independent consultants tend to have much better rates, without the overhead, and without bureaucratic structure, you benefit from working directly with a consultant rather than a team with varying opinions and agendas.

Case and point, while working with several Ivanti Business Partners, it was not uncommon to spend 2 hours a week on status calls with the Ivanti Project Manager, Ivanti Account Manager, Ivanti Territory Manager, Ivanti Customer Service Manager, and Ivanti Business Partner Sales Person. That translated into 8 hours per month of consulting time, and worse yet, days of additional effort as managers had their own agendas and the customer instead of getting the consultative experience, ended up confused and unable to make informed decision based on expert advice.

Ivanti Implementation Packages

With my 25+ years of Ivanti HEAT ISM consulting experience, worldwide, the following Ivanti Implementation Packages have been designed to give customers a direction and starting point but come with the caveat that as mentioned above, estimated effort sizing is required based on the roadmap and deliverables. As always a free no-obligation Discovery Session is needed to tailor an Implementation package to your business requirements.

ivanti implementation packages - former kifinti solutions consultant -best-practices-heat-ivanti-service-manager-ism-itsm-itam-ivanti asset manager

Starter Package | 19 Days

This package is designed for organizations newly implementing Ivanti Service Manager, wanting to fine-tune their system, streamline existing processes, build simple integrations, or requiring basic configurations changes for fundamental ITIL processes.

Critical Path Package | 50 Days

An extension to the starter package, for organizations wanting to take the Ivanti Service Manager Implementation to the next level with advanced configurations and processes, complex integrations, and in-depth configuration of fundamental ITIL processes.

For example one of the following: Procurement, Hardware Asset Management, Software Asset Management, Change Requests, HR Onboarding/Off Boarding.

Ultimate Success Package | 100 Days

For those organizations serious about leveraging Ivanti Service Manager to the max and taking their Ivanti Implementation to the highest level, with advanced configurations, advanced processes, complex, integrations, in-depth automations, workflows, and several complex integrations.
For example one or more of the following: Procurement, Hardware Asset Management, Software Asset Management, Change Requests, HR Onboarding/Off Boarding.

In Summary, my Ivanti Implementation Packages are designed as a guide and starting point for establishing a scope of work and roadmap to excellence.

A Discovery Session is needed to asses which package is best.