Видео

awesome

Love the T-Shirt

The voices of experience here. So many great tips on licensing

Key Bookmarks 2:38 Craig Guarente from Palisades Compliance 35:35 Pamela Fulmer, Attorney from Tactical Law Group 1:10:59 Rory Canavan: Machine Learning & SAM 1:38:54 Jeffery Tefertiller, The Building Blocks of an Effective Asset Management Program 2:05:32 Piara MacDonnell, Framework to Responding to an IBM License Audit 2:34:54 Alexander Golev, SAMexpert. I did not catch the title, but for my coworkers, this is the one has references to both VMWare and Microsoft These are rough estimations on when each speaker presents. All speakers are worth listening to at least once.

Thank you so much for posting these as I had work conflicts for the day. I took away a lot of information from each and every speaker. (Your Pink23 and Pink24 friend)

I really resonate with your discussion on software spend waste. ***Tech Leaders*** Stop spending and adding more software to your suite of software when you aren't currently at a resource count/capability/maturity to even leverage the benefits of your suite of products/services. It's simply not well thought out decision making. "Start where you are" (An ITIL Guiding Principle)... and work on maximizing the benefits and capabilities of the software you already have under license and pay a great deal of money for.

Many big, successful, and long lasting software providers are great at creating well thought out switching costs so that their customers remain their customers for the long run. Bill Gates and Microsoft showed the Corporate World mastery in this shifty kind of technique/retention tactic. I'm curious what others think about switching costs? Do you think it's savvy business tactics or should it be frowned upon? Does it fall within what is business ethical or is it unethical?

I definitely like the ADKAR method as it is very industry agnostic.

I would argue that many headaches could be saved by thinking of OCM as early in the development as possible.

I think a step is either assumed or missing: you mentioned layering in best practices. Conceivably, there will be a gap between current practice and the newly developed practice (with stakeholder buy in) - an action plan to close those gaps needs to be developed. Then, the metrics to measure should include at least to prove the new practice is being practiced.

Thank u

Super informative, thanks for uploading and sharing Jeffrey!

awesome

wow

Thank you very much for explaining so well the details of SLA.

Integrity over Image Truth over Convenience Honor over Personal Gain

A good first question to ask a user is ‘do you have a ticket reference number ?’ This at least helps the avoidance of raising a ticket and discipline . Agree with the point about through the lens of the customer….has to be easy to do

This was helpful. I appreciate your explanations.

Great video, Loved it.

Very helpful thank you.

Please create video on service now

Please make video on service now

Please make video on service now

Nice work Jeffrey - can I suggest adding some text to the screen as bullet points, or include the use case in the video description.

The idea of "focusing on value" grabbed me. As a Sales Engineer, my biggest challenge is getting product development to value what the customer's needs are instead of them developing what they want to give the customer. Product management tends to side with development, yet neither actually knows the customer... frustrating.

Yes so true how the concept of ‘rip it up and start again ‘ is the only answer !! Re use / start where you are … at least you know the risks going forward …..as that’s where you are ! 😀

Thank you Jeff. I wish to learn more on SMO, is there a way I can contact you please?

Could you give examples of: "Pure" Asset, "Pure" CI and "Hybrid" please. Many thanks!!!

Fantastic explanation

Would it be possible for you to get me in touch with David? Do you have a private email address of him?

Before opening a problem case for each major incident, check your problem database history. It's possible the same fault happened in the past and thus you should link the recent incident to the problem case, re-open it if closed. No point opening problem case for each major incident, you will end up with duplicate problem cases, all with the one incident linked to each problem case. Makes no sense. Have one problem case with all reoccuring incidents (major or not) of the same issue/fault linked into it. It's one investigation. Imagine if WINDOWS 10 kept crashing with error code ABCDE on every users laptop across the globe and MICROSOFT were getting 1000s of major incidents logged by hospitals, air traffic control, banks etc... They wouldn't open 1000s of problem cases as well. One problem case, one investigation to find root cause, one case containing all the problem progress a the solution eventually. so, don't open new problem case for every major incident, check your history first, you will avoid creating a mess of duplicated problem cases.

my interviewer asked what is configuration item.. i said it could be an application/program/ or a code that needs to be upgraded or deleted or modified according to need of the service

Amen! Very great point! Just sorting that out now actually, hits close to home. Not fun to sort but will be worth it going forward.

Another wonderful discussion with David!

👍🏻

Thanks for one more great video for helping understand configuration items, baselines and change management.

Very well explained

Bang on !!

Thanks, it was helpful

great

Good explanation ... Subscribed ♥️

Its true, I've been into this situation where tools usage are now defining the process and actually missing the value of the basic ITSM optimized process which is designed to meet all your needs. Managers need to understand not to tweak the process according to the tool instead tweak and design the tool to match ITIL standards. That is serious work in beginning but goes smooth on-field very soon.

Jeffrey, I need your help

I must talk to you

Loving this channel! Thank you for sharing your knowledge, it’s been very beneficial to my growth.

nice

That’s really great conversation :) open and positive and valuable :) thanks for sharing!

Sounds like a great guy you had that chat with... ;-). Great video!

Thanks for having me, Jeffrey. Good luck and all the best!