Identifying the Need for Software | Phase 1 of the Software Asset Lifecycle скачать в хорошем качестве

Identifying the Need for Software | Phase 1 of the Software Asset Lifecycle

Learn more here: https://www.anglepoint.com/lightning-... This phase includes understanding why and how requests for software are generated in your organization. You may be thinking – why do we have to identify need at all? If I request software, then I obviously need it, right? A mature SAM program always tries to optimize wherever possible – so while there may be a need for software, it is important that money is saved instead of automatically spent with each request. It is important to understand WHY and HOW software requests are being generated. If I asked you to compare how many software requests in your organization follow a controlled and standard channel versus an ad-hoc process, would you know? Would you even know who you could ask to find out? What Software Asset Management should support in the Identifying Need phase is a controlled, gatekeeping function that ensures needs are supported by analysis, and that any non-standard requests are appropriately scrutinized. In this way, you will ensure that potentially risky, non-managed or non-controlled software will not be freely entering your organization without an approval or audit trail. Each request for software should be justified with appropriate due diligence. The business area in your organization requiring software should perform an analysis versus their functional requirements, budget availability, and strategy so they are able to justify spending money on software. In some cases, this is as simple as an additional headcount needs to have Adobe Acrobat Professional to perform their job duties, in which case an operating budget would easily cover the proposed expense. In others, it could be a longer and more complex justification process to support a larger project or investment. If a software request can NOT justify a need for spending money or is NOT accompanied by sufficient analysis, then it should be denied by the Software Asset Management team. This becomes less of a financial management function and more of a corporate governance function. It is recommended that you develop a policy to support adherence to this behavior, and support a culture of due diligence within your organization. Best practice is to develop a Software Catalog which includes pre-approved items for end users to request. Each requestable item should include a cost. This will drive accountability of the business area requesting software since they will see the cost impact and need to be able to justify the expense.