IT Governance

Three Considerations Regarding Software Asset Management

Ryan Ogilvie, in this article in ServiceManagementJourney.ca, discusses three basic considerations surrounding software asset management – let’s take a look at them.

Operations

How software is governed is one of the foremost considerations when software asset management is discussed. In practice, this refers to the policy and process to request, approve, procure, manage and retire what organizations have in their software library. This is not formally outlined in most companies and contributes to problems. When it is outlined, it provides the right amount of software, to the right people, and in a way that makes business sense.

That aside, people should be aware of what some software does do, or indeed what it doesn’t. This will prevent them from requesting professional versions when the standard version will do – this will reduce costs, while also reducing risks when installing it on a server.

In order to be truly in charge of software management, we should also have a good understanding of where documents such as contracts and license agreements are stored, and who manages them.

People

Besides the obvious security aspect of allowing people to be the admin on their individual workstations, there is also the risk of people installing software which they believe to be free, without coming to grips with the terms and conditions which could come into play down the road.

In an effort towards better management, making sure that business has a good dialog with IT will ensure that fit for purpose software is always made available.

Start With the End in Mind

Software isn’t designed to fix things, but instead to merely help manage processes that are in place. Therefore, if a formalized process isn’t in place, it should be implemented at the earliest. If some process is indeed in place, use it to identify holes, and make efforts to plug these holes. That aside, businesses should set themselves up for success by making agile improvements that can be reviewed, measured, communicated, and repeated.

This exercise can be a significant undertaking, so do enlist the help of experts in the field. Also, use the considerations mentioned above to chart out an executable road-map.

Click on this link to view the original article in full: https://servicemanagementjourney.ca/2018/10/software-asset-management-basic-considerations/

Tags

Sapna Hiremath

Sapna S Hiremath is currently working as a Content Specialist Lead for CAI Info India. With experiences of having worked for newspapers after pursuing a Master's in Mass Communication and Journalism, she has worked in the thriving fields of Search Engine Marketing, online shopping and healthcare. Being an avid traveler, she likes being in the serene landscapes of nature, but also likes being around friends.

Related Articles

Back to top button
Close
X

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.