Martin – I totally agree with the point you make about SAM being governance, however there have been cases where SAM has actually added value by recommending software to use. For example, a user wants to purchase software X, but that costs £1000. The user says they will be happy with an alternative, as long as it has the same features and functionality. By looking around and identifying a cheaper piece of software SAM can add value and save money.
Yes, you could argue that this isn’t SAMs job and that the user should be looking for alternative software. But sometimes, a quick search for a cheaper alternative can save you an awful lot of money so why not do it?
I also agree with others that the creation of a software catalogue is the ideal way to manage your application portfolio. However, a software catalogue should still be restricted – it is not an invitation to a free-for-all! There may be a specific piece of security software that only the IT Security department should have access to – so whilst it is approved and in the catalogue it is not software that should be deployed globally. ALL software should be assessed on functionality, price and compatibility – along with your organizations standard security checks before being added into the software catalogue. And of course, you need licenses!!
Non-approved software really needs scrutiny. If it is a single user requesting a piece of bespoke software, then should you really package the software and add it to your software store? Of course it needs to be checked and the standard process followed – but questions on whether or not the effort and time should be spent on packaging and adding into the software store is another matter.
If it is a single install and approved, then of course it should still be added into the software catalogue!