Skip to main content

Service Offerings - Activities for Service Portfolio Management

Service Portfolio Management (SPM) is a process that is defined by ITIL best practices in the Service Strategy Lifecycle Stage.  The initiation of activities for Service Portfolio Management is often a result of changes to strategic plans or the identification of a service improvement plan and are triggered by a proposal that must have executive approval to proceed.  For existing services, Service Portfolio Management considers investments that have already been made along with new investments required.  The combined may result in the service being too expensive for what the business will achieve.  Investment decisions will need to be made.  There are many possible procedures and workflows to fulfill all the details of this process but overall the activities can be clearly understood with four high level process activities.

Define – In this stage of the process SPM must document and understand existing and new services.  Every proposal for a new or changed service must be accompanied by a full blown business case.  This stage of the process defines desired business outcomes, opportunities and the requirements for the new or changed service proposed.  The customer and consumers of the service are defined. The major inputs and outputs, performance and other non-functional requirements (warranty requirements) will all provide data to ascertain anticipated ROI as well as the type of return the customer needs.  Constraints and how much the customers are prepared to spend will also be identified through this stage of the process.  Regulatory or legal requirements and any applicable standards must be clearly defined to complete the level of information required to build a clear and appropriate service model.  The success for all other activities is based on clear and detailed information defined here.

Analyze –  Here is where we determine whether the service can optimize value. One of the first steps is to define how services will be analyzed, what level of data is required and who will perform the analysis.  In some organizations, the analysis is performed by a pool of senior architects, managers or even a strategic architecture board to evaluate services.  The analysis will need to consider what the long-term goals of the organization are, how the service being analyzed contributes to those goals and what capabilities and resources will be needed to deliver the service.

Approve – This is where “change management” plays a big role in the SPM process and where resources are authorized.  Because this is a major or strategic change that gets processed through the SPM process an authority matrix is often used to approve the new or changed service.  All the information and outputs from the Define and Analysis activities will be evaluated.

Charter – This is the final strategic activity to be performed for the proposed new or changed service before it moves into Service Design.  Charter has two meanings.  One is a verb which implies that the new service (or changes to the existing service) has been commissioned by the customer or business executives.  Within the Service Portfolio Management context a charter is a noun referring to a document which is used to authorize work to meet defined objectives, outputs, schedules and expenditure.  Charters are normally used to initiate the design stage of projects.

Design Coordination, Financial Management and other critical processes will need to integrate as they have a key role to play to ensure that wise business decisions are made throughout Service Portfolio Management activities.

For more information regarding Service Offerings and Agreements (certification and training)   click here!


Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…