Governance of software assets
Introduction
The programme “Governance of software assets” addresses a professional task within Information Technology and Technical Services, connecting the subject with case data, user requirements and the expected deliverable. Participants define the question and scope of responsibility, then select the evidence needed to assess the situation, compare options and prepare a reviewable practical deliverable.
Learning progresses from infrastructure and service mapping to capacity and availability planning, connecting analysis with selection, verification and follow-up. Participants develop an application pack for “Governance of software assets” containing the case definition, inputs, alternatives and review findings, with the assumptions, constraints and responsibilities that determine whether the recommendation is suitable.
The approach combines concepts, review of training documents and data, decision exercises and presentation of findings. Examples are adapted to participant experience, with a clear distinction between classroom learning and workplace execution under the relevant professional authorisations and approved institutional procedures.
Objectives
- Define the scope of “Governance of software assets”, its expected result, its users and its acceptance criteria.
- Organise data for infrastructure and service mapping and assess its sources, completeness and limits of use.
- Apply capacity and availability planning and connect it with the programme task and its professional constraints.
- Analyse alternatives through service operations and support, explaining the selected option, its risks and its requirements.
- Define verification evidence for change and recovery, review points and matters requiring escalation.
- Prepare a follow-up plan for cost and service quality with responsibilities, indicators and reassessment triggers.
Programme topics
Learning area 1: Infrastructure and service mapping
- Define infrastructure and service mapping and its scope, explaining how it relates to the professional task and the required case result.
- Review component register, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
- Analyse service dependencies using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
- Compare options for infrastructure and service mapping against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
- Prepare a checklist linking evidence for component register and service dependencies, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
- Apply this learning area to the “Governance of software assets” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.
Learning area 2: Capacity and availability planning
- Define capacity and availability planning and its scope, explaining how it relates to the professional task and the required case result.
- Review demand volume, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
- Analyse capacity indicators using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
- Compare options for capacity and availability planning against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
- Prepare a checklist linking evidence for demand volume and capacity indicators, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
- Apply this learning area to the “Governance of software assets” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.
Learning area 3: Service operations and support
- Define service operations and support and its scope, explaining how it relates to the professional task and the required case result.
- Review support ticket register, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
- Analyse service levels using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
- Compare options for service operations and support against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
- Prepare a checklist linking evidence for support ticket register and service levels, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
- Apply this learning area to the “Governance of software assets” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.
Learning area 4: Change and recovery
- Define change and recovery and its scope, explaining how it relates to the professional task and the required case result.
- Review change impact assessment, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
- Analyse recovery plan using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
- Compare options for change and recovery against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
- Prepare a checklist linking evidence for change impact assessment and recovery plan, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
- Apply this learning area to the “Governance of software assets” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.
Learning area 5: Cost and service quality
- Define cost and service quality and its scope, explaining how it relates to the professional task and the required case result.
- Review operating cost, identifying sources, units and reference periods and recording gaps and conflicts before using the information.
- Analyse user satisfaction using case documents and data, distinguishing direct measurements from estimates and assumptions and discussing their effects on the decision.
- Compare options for cost and service quality against requirements, resources and dependencies, documenting why an option is appropriate and the limitations affecting its use.
- Prepare a checklist linking evidence for operating cost and user satisfaction, identifying the reviewer, acceptance criterion and action needed when a condition is not met.
- Apply this learning area to the “Governance of software assets” exercise and update the work pack with documented inputs, analysis and observations to carry forward to the next learning area.
Outputs
- An integrated application pack for “Governance of software assets” showing the path from the professional question to the finding and recommendation.
- An input, assumption and gap register with information sources and verification owners.
- A documented analysis of case alternatives linking capacity and availability planning with execution and resource requirements.
- A professional checklist defining acceptance criteria, review points and closure evidence.
- An action plan identifying priority, owner, due date, follow-up indicator and dependencies.
- A final presentation of findings, limitations, open questions and requirements for institutional application.
Who should attend
- Specialists, supervisors and work coordinators in Information Technology and Technical Services whose responsibilities relate to the programme subject.
- Team leaders, work coordinators and reviewers who assess deliverables and coordinate disciplines.
- Practitioners preparing for broader responsibilities in the discipline who have basic familiarity with the work context.
Participation requirements and delivery methodology
- Basic subject knowledge or professional experience sufficient to understand the terminology and case documents.
- Use non-confidential training data; participant examples may be discussed after removing identifiers and information not authorised for sharing.
- Interactive explanations, individual and group exercises, case analysis, peer review and presentation of applied work.
- Assess progress through input quality, analytical reasoning, deliverable clarity and responses to review comments.
- Programme duration: five training days and twenty-five training hours.
- Delivery in Cairo at UHRDA headquarters in Arabic; English delivery is available by agreement.
Conclusion
The programme “Governance of software assets” concludes with a practical pack connecting specialist knowledge with evidence, alternatives and responsibilities. Progress is demonstrated by the participant’s ability to explain choices, document their limits and produce work that users and reviewers can understand and follow up.
Applying this approach in the organisation supports better questions, stronger information and clearer team coordination. Workplace application is planned around the asset or service, available data and review requirements, with impact monitoring and updates when conditions change.
