This course outline introduces software asset management (SAM) for practitioners. It was written as a two-to-five-day instructor-led or virtual course and is organized in nine modules, each with key topics, a reference table and exercises.
Audience: IT managers, procurement specialists, software administrators, licensing specialists, compliance officers and other stakeholders involved in software life cycle management.
Learning objectives:
- Understand the fundamental principles and benefits of effective software asset management.
- Become familiar with common SAM frameworks, standards and best practices (for example ISO/IEC 19770 and ITIL).
- Learn to categorize, track and maintain software assets and entitlements.
- Acquire skills to manage software licensing (on-premises, cloud and hybrid) and vendor relationships.
- Develop processes for full software life cycle management and governance.
- Measure and optimize SAM performance through metrics and continuous improvement.
Duration: approximately two to five days of in-person or virtual training, or spread across multiple sessions.
Module 1: Introduction to software asset management
- What is software asset management?
- Definition: SAM is a set of business practices that support the use and control of software assets within an organization, ensuring compliance, optimizing costs and reducing risk.[1]
- Importance: modern organizations rely heavily on software for operations, making effective SAM crucial.
- Business drivers for SAM
- Financial implications: budgeting and cost optimization.
- Compliance and legal risks: avoiding fines or legal disputes with vendors.
- Operational efficiencies: streamlining processes and improving service delivery.
- Key SAM terminology
- License entitlements
- EULA (end-user license agreement)
- Maintenance and support agreements
- Cloud and SaaS subscriptions
- How SAM fits into IT governance
- Integration with ITIL processes (configuration management, change management).
- Alignment with broader IT governance frameworks (for example COBIT).
Table 1: Common software license models
| License model | Description | Example vendors |
|---|---|---|
| Perpetual | One-time purchase, use indefinitely (often with optional annual support) | Microsoft (older models), Adobe (older) |
| Subscription / SaaS | Time-based subscription (monthly, yearly), includes updates and support | Office 365, Salesforce |
| Per user | Licenses associated with individual named users | Many cloud apps (Zoom, Slack, etc.) |
| Per device | License tied to a specific machine or device | Some engineering and CAD software |
| Concurrent / floating | A pool of licenses shared among multiple users, of which only a set number can be in use at once | Some CAD, engineering or virtualization tools |
| Open source | Freely available, but subject to specific open source license terms (for example GNU GPL) | Linux distributions |
The source table was adapted from ISO/IEC 19770-1 and The ITAM Review. For the cited treatment of each model see Software licensing models.
Activities and exercises:
- Group discussion: share real-world anecdotes of compliance issues or cost overruns due to poorly managed software.
- Case study: examine a short scenario where an organization lacks visibility into its software usage, leading to unbudgeted true-up costs.
Module 2: SAM frameworks, standards and best practices
- Overview of common SAM frameworks
- ISO/IEC 19770 series: a global standard family for software and IT asset management programs.[1]
- ITIL: best practices for IT service management, including guidance on asset and configuration management.
- IAITAM (International Association of IT Asset Managers): offers certifications and operational guidelines.[2]
- ISO/IEC 19770-1 explained
- Process areas, roles and responsibilities.
- Importance of documentation, continuous improvement and evidence-based decision-making.
- ITIL and SAM
- ITIL asset management versus configuration management.
- How SAM processes fit into the broader ITIL service life cycle.
- Best practices for establishing a SAM program
- Gaining executive sponsorship.
- Defining clear policies and procedures.
- Ensuring continuous improvement through periodic reviews and audits.
Table 2: Comparison of key elements in ISO/IEC 19770-1 and ITIL
| Aspect | ISO/IEC 19770-1 | ITIL (v4) |
|---|---|---|
| Focus | SAM-specific standards and processes | Broad IT service management framework |
| Scope | Software assets (including licenses) | End-to-end IT services, including hardware and software assets |
| Process orientation | Detailed requirements for compliance, governance, life cycle | Best practices for the service life cycle (strategy, design, transition, operation, continual improvement) |
| Key strength | Formal structure for managing software assets | Integrates SAM with incident, problem and change management |
| Primary reference | ISO/IEC 19770-1:2017 | ITIL 4 (AXELOS, 2019) |
Activities and exercises:
- Framework comparison chart: participants create a summary comparing ISO/IEC 19770-1, ITIL and IAITAM guidelines.
- Policy development workshop: draft a short SAM policy statement tailored to your organization.
Module 3: The software asset life cycle
- Life cycle stages
- Planning / request: needs assessment and budgeting.
- Acquisition / procurement: vendor selection, negotiations.
- Deployment: installation, configuration, distribution.
- Maintenance / support: patches, updates, technical support.
- Retirement / disposal: decommissioning, license reclamation, data erasure.
- Key considerations at each stage
- License models and terms.
- Renewal timelines and upgrade paths.
- Version control and ensuring compliance.
- Integrating SAM throughout the life cycle
- Capturing data at each touchpoint (requests, changes, disposals).
- Cross-functional collaboration (finance, procurement, IT operations).
Table 3: Sample software asset life cycle with stakeholder involvement
| Life cycle stage | Primary stakeholders | Key SAM activities |
|---|---|---|
| Planning / request | Business unit, IT, finance | Requirements gathering, cost estimation, approvals |
| Acquisition | Procurement, legal, IT | Vendor evaluation, contract negotiation, licensing |
| Deployment | IT operations, end users, security | Installation, configuration, compliance checks |
| Maintenance | IT support, security, SAM manager | Monitoring usage, patches, audits, renewals |
| Retirement | IT operations, SAM manager, finance, legal | License harvesting, disposal documentation |
Activities and exercises:
- Life cycle mapping exercise: participants map one key software product through its entire life cycle, identifying risks or improvement areas.
Module 4: Software license management and compliance
- Understanding license models
- Per seat, per user, per device, concurrent, site license, SaaS licensing and others.
- Negotiating volume licensing agreements (for example the Microsoft Enterprise Agreement).
- Compliance requirements and challenges
- Common misunderstandings about usage rights.
- Organizational changes (mergers, acquisitions) affecting license entitlements.
- Bring-your-own-device (BYOD) and remote work implications.
- Managing audits and vendor relations
- Typical audit triggers (vendor business objectives, random checks).
- Preparing documentation and evidence for audits.
- Negotiation tactics to maintain healthy vendor relationships.
- Inventory management tools and techniques
- Software discovery tools (agent-based versus agentless).
- Software identification tags (ISO/IEC 19770-2)[3] and data normalization.
- Integration with a CMDB (configuration management database).
Activities and exercises:
- License review simulation: review example EULA terms to identify potential compliance gaps.
- Audit readiness checklist: develop a short checklist to prepare for a software vendor audit.
Module 5: SAM technologies and tooling
- SAM tool categories
- Discovery and inventory tools: for example endpoint management and ITSM platforms with discovery features.
- License management and optimization: tools that track entitlements against usage.
- Tool selection criteria
- Alignment with organization size and complexity.
- Integration capabilities with existing ITSM, ERP and HR systems.
- Reporting and analytics features, ease of use.
- Implementing and maintaining SAM tools
- Phased deployment approach (pilot, rollout, optimization).
- Importance of data cleansing and normalization.
- Ongoing calibration and integration with other systems.
- Automation and integration opportunities
- Automated discovery and inventory updates.
- Integration with HR (joiners, movers, leavers) and finance systems (vendor payments, budget forecasting).
- Automated alerts for license overuse or approaching expiry.
Table 4: Example SAM tool comparison
The table below is illustrative course material, reflecting the course authors’ view as of 2025; it is not an endorsement or an independent evaluation.
| Tool | Key features | Target organizations | Strengths | Challenges |
|---|---|---|---|---|
| Flexera | License compliance, optimization, cost analysis | Mid to large enterprises | Comprehensive coverage | Higher cost, complex to implement |
| Snow Software | Discovery, license metering, analytics | Mid to large enterprises | Strong discovery and analytics | Requires careful configuration and maintenance |
| ServiceNow ITAM | Integrated with ITSM, workflows | Enterprises with an existing ServiceNow ecosystem | Process integration | Can be expensive for smaller organizations |
| Microsoft SCCM | Windows-centric endpoint management | Primarily Windows-heavy environments | Strong OS-level integration | Limited cross-platform capabilities |
Activities and exercises:
- Tool evaluation matrix: participants create a requirements list and score candidate tools for their organizational context.
- Hands-on walkthrough (if possible): demonstrate a SAM tool’s workflows (inventory scan, compliance report, and so on).
Module 6: Implementing SAM: governance and organizational structures
- Stakeholders and responsibilities
- Executive sponsor (CIO, CFO).
- IT operations, procurement, licensing specialists, legal and compliance, finance.
- Possible role of external consultants or managed services.
- Developing a SAM governance framework
- Formal SAM policies and procedures.
- Roles and accountability (use a RACI matrix).
- Approval processes and change management integration.
- Risk management and internal controls
- Identifying high-risk software (for example expensive licenses, frequently audited vendors).
- Monitoring usage, implementing license check-outs.
- Ensuring separation of duties for procurement and compliance checks.
- Budgeting and forecasting
- Aligning software procurement with corporate objectives.
- Negotiating volume discounts.
- Accurate renewal forecasting, tracking usage to justify spend.
Table 5: Example RACI matrix for SAM governance
| Task | Responsible (R) | Accountable (A) | Consulted (C) | Informed (I) |
|---|---|---|---|---|
| Develop SAM policy | Licensing manager | CIO | Legal, procurement | IT teams, finance |
| Vendor license negotiations | Procurement lead | CFO | Licensing manager, legal | CIO, department heads |
| License inventory maintenance | SAM administrator | IT director | End users, procurement | Finance, security |
| Audit preparation and response | SAM administrator | CIO | Legal, procurement | Department managers |
Activities and exercises:
- RACI matrix exercise: participants build a RACI matrix for their own organization.
- Governance playbook: draft a SAM governance outline, including policy references, roles and processes.
Module 7: Measuring SAM performance and reporting
- Key performance indicators (KPIs) and metrics
- License compliance rate (percentage of software in compliance).
- Cost savings and cost avoidance (differences in budget after optimization).
- Software utilization metrics (for example shelfware identification).
- Audit frequency and outcomes.
- Data collection and analysis
- Balancing detailed data against executive-level summaries.
- Communicating findings to technical, financial and executive audiences.
- SAM reporting best practices
- Real-time dashboards for immediate insights.
- Scheduled reporting (monthly, quarterly) to highlight trends and return on investment.
- Linking SAM metrics to strategic objectives (for example cost reduction, risk mitigation).
- Continuous improvement
- Periodic process reviews for efficiency and effectiveness.
- Adapting to changing business models (for example more SaaS).
- Reassessing targets as maturity grows.
Table 6: Example SAM KPIs and their rationale
| KPI | Calculation | Why it matters |
|---|---|---|
| Compliance rate | (Compliant installations / total installations) × 100 | Indicates how close you are to vendor licensing requirements. |
| License utilization | (Actively used licenses / total purchased licenses) × 100 | Identifies over- or under-licensing and potential cost savings. |
| True-up cost avoidance | Actual true-up costs minus projected or historical true-up costs | Demonstrates the financial impact of effective SAM practices. |
| Audit readiness index | Qualitative score based on documentation, processes and data completeness | Reflects preparedness for vendor or regulatory audits. |
| Re-harvested licenses | Total reclaimed licenses per quarter | Measures efficiency in reusing unused licenses. |
A compliance rate across a whole estate is a simplification: compliance is determined per product and per license metric in an effective license position.
Activities and exercises:
- Metric definition workshop: choose three to five KPIs relevant to your organization and discuss how to track them.
- Reporting case study: develop a mock executive report on software compliance status and cost savings.
Module 8: Maturing and optimizing your SAM practice
- SAM maturity models
- Levels are often described as ad hoc, basic, standardized and optimized.
- Characteristics at each level (processes, governance, automation, continuous improvement).
- Roadmap for advancement
- Creating a long-term vision with short-term milestones.
- Prioritizing initiatives (tool upgrades, process improvements, staff training).
- Building an agile approach to respond to new technologies (for example containers, microservices).
- Industry trends and future directions
- Cloud and SaaS implications for license tracking and cost management.
- Managing hybrid environments (on-premises, cloud, containerized applications).
- AI-driven analytics for usage and forecasting.
- Case study: high-maturity SAM implementation
- Examples from organizations that have achieved an optimized SAM practice.
- Key takeaways on cost control, compliance and minimized risk.
Activities and exercises:
- Self-assessment exercise: participants rate their organization on a simple maturity model checklist.
- Future planning session: outline a one- or two-year roadmap detailing steps toward the next maturity level.
Module 9: Common challenges, pitfalls and best practices
- Challenges and pitfalls
- Underestimating the complexity of licensing.
- Lack of executive buy-in or budget.
- Siloed processes (procurement does not communicate with IT).
- Overcoming resistance and championing SAM
- Building a compelling business case (demonstrate return on investment).
- Celebrating quick wins to maintain momentum.
- Engaging stakeholders through transparent communication and training.
- Best practices recap
- Centralized repository of license entitlements.
- Periodic internal license reviews and true-ups.
- Ongoing stakeholder engagement, training and governance.
- Case studies of failure
- High-profile audit penalties and their root causes (lack of oversight, incomplete inventory).
- Missed renewals leading to service disruptions.
Activities and exercises:
- Role-play: pitch the benefits of SAM to a reluctant executive sponsor or department head.
- Troubleshooting scenarios: participants brainstorm solutions for a series of fictional SAM dilemmas.
Conclusion
The course aims to give participants a comprehensive understanding of software asset management principles, tools and practices. Following standards such as ISO/IEC 19770 and integrating with frameworks such as ITIL helps an organization stay compliant, optimize software spend and reduce risk.
Key takeaways
- Holistic approach: SAM is more than tooling; it requires clear governance, defined processes and engaged stakeholders.
- Life cycle integration: embedding SAM into each phase of the software life cycle yields proactive cost management and reduced risk.
- Continuous improvement: regularly measure performance (KPIs) and adapt SAM strategies to evolving business and technology landscapes.
Further reading
The original course cited the following works, which are not freely linkable:
- AXELOS (2019). ITIL Foundation: ITIL 4 Edition. AXELOS.
- Deloitte (2022). Software License Audit and Management Insights. Deloitte publication (not located online).
- Gartner (2023). Market Guide for Software Asset Management Tools. Gartner Research (subscription).
- The ITAM Review, an industry news site: itassetmanagement.net.