Voted Best Answer
Jan 07, 2016 - 01:42 PM
We get asked "How many should be in my SAM team" quite often. Either by folks that are drowning and want to expand their team or by senior management teams setting up for the first time wanting to know what their peers do for comparison.
My honest but dull consultant answer is "it depends".
By all means look at what others are doing - but the most accurate way of building a team is to ask how much risk have you got now and how much do you want?
By means of an example - If your organization had a serious support issue creating hundreds of incidents / service desk tickets - you would invest in enough service desk operators to manage the issue to an acceptable level. How many is difficult because 'acceptable' is different by industry.
Similarly for ITAM, how much risk do you have, how much opportunity is there for saving, what resources do you need to achieve that? The size of your team will vary significantly if you just want to remove the risk of audit for a couple of large vendors compared to running a world class ITAM practice that is fully automated and self-funding.
Tools will certainly help with some of the heavy lifting, but it will also be dependent on your internal structure:
hundreds of subsidiaries and countries or one central location
handful of standard builds in one network or laissez faire attitude to installs over hundreds of different devices
Estate complexity and licensing agreements (e.g. 10,000 seat art college with Microsoft and Adobe might need less resource than a 1,000 seat oil and gas company with complex engineering apps)
Acquisitive company or fairly slow and steady
Sorry for the wooly answer, but it's a wooly problem :-)