Prioritise Scope of APM Change
The scope of proposed changes to the application portfolio should be based on their strategic value, business criticality, and future requirements. Prioritisation metrics for an application are captured directly in the relevant information system object using the provided metadata fields. Prioritisation can be done in different ways depending on the nature of the organisation, the services they offer, and any other relevant business considerations.
Key things to consider regarding the prioritisation of APM changes could be:
The business capabilities an application supports, application performance, risks related to the application’s lifecycle and infrastructure, considerations of application support, and the organisation’s strategic imperatives.
Insights identified during the evaluation stage of the journey will be used to propose and prioritise improvements to the portfolio, as well as projects and initiatives to effect the necessary changes. This should be considered with the broader organisational strategy, and efforts must be aligned and coordinated.
Action plans
Action plans can be created and managed directly from the application architecture diagram in the analysing & improvement dashboard, and existing projects can be viewed via the standard improvement schedule feature.
A simple method of creating a new project or initiative is to use the repository explorer to create a new project object.
Prioritising APM changes will require allocating resources and budgets based on the prioritisation criteria and leveraging this information to create and monitor a roadmap for future application investments.