Software asset management (SAM) is not as terrifying to implement as previously thought. In a concise post at his blog, Joe the IT Guy gives a quick top-ten list for successfully creating a SAM process. Everything is easier as a list:
- Know your audience.
- Know what you are trying to model.
- Align your processes to your SAM strategy.
- Align your processes with IT.
- Align your processes to the business strategy.
- Process owner assignment
- Process review
- Look and feel
The Process of Process-Building
The first two steps are dependent upon acquiring the appropriate knowledge. Depending on whom you are trying to reach, more than one physical document may be necessary, and process maps can be the answer to this. Standard operating procedures can also show a keystroke by keystroke explanation of what is happening. It is equally as important to define the objectives of the process from the very beginning.
The next three steps involve aligning different elements of the process. First, it is vital that there is no doubt what the role of the process is in the bigger picture. Second, if a process has a prominent impact beyond the scope of SAM, it is important to reinforce that importance. Finally, take this opportunity to promote exactly what it is IT does for a company and what they offer. IT is not merely a utility; they have a grand purpose.
The next few tips encompass working with other people. In a collaborative effort, identify the stakeholders that need to be communicated with. It is far easier to gain someone’s trust by including them in the decision-making process than it is to present them with an idea already thought up. Along with this, the process should be tested. The expected results should be delivered, and if they are not, re-engineering should not be feared. The processes need an owner, and one who will take on the responsibility of overseeing the running of the new processes. There needs to be one substantial advocate for this change.
In order to maintain relevance, the process should be reviewed. This ensures objectives are met. The process should finally also align with standard company practices of documentation, exuding the preordained look and feel, preventing a business culture shock.
Joe says these tips could be utilized beyond the scope of SAM, but they are specifically designed for this particular process. You can read the original post here: http://www.joetheitguy.com/2015/10/08/write-software-asset-management-process-part-1/