Skip to main content

The Service Portfolio and Portfolio Management

The Service Portfolio represents the complete set of services that is offered and managed by a service provider.  It corresponds to the entire lifecycle of all services and is made up of three sections.  The first, the Service Pipeline (proposed or in development) denotes the future stance the organization is going to take in meeting customer requirements and aligning to the future business strategy.

Next is the Service Catalog (live or available for deployment) which is what the service provider is currently delivering and maintaining to meet the organizations current and near future goals and objectives. 

Finally we have the Retired Services, which have been deemed no longer valuable enough to sustain their continued delivery, but may need to be continued to be supported for some defined time to meet some regulatory or legal requirement.

The Service Portfolio is an integral tool in helping us define perspective and position. It is a tool for our customers/business and acts as a means for comparing our services against our competitors. What’s that? You’re an internal IT service provider and therefore are not in competition?  Just remember, you are always in competition.  There will always be someone knocking at the door saying they can do it better, faster and cheaper.  The Service Portfolio is not only a tool for your customer but for you as well and should be the basis of a decision framework which allows you to answer the following strategic questions:

  • Who are my customers and what services should I be offering to them?
  • Why should a customer buy these services?
  • Why should they buy them from us?
  • What is the pricing or chargeback structure?
  • What are our strengths, weaknesses, priorities and risks?
  • How should our resources and capabilities be allocated?

Given the above, the purpose of Portfolio Management is to ensure that we are providing the right mix of services to align and balance with the overall investment in IT and that those services ensure the ability to create the appropriate business outcomes. In this way we also align the design, transition and operational activities with the value of our services.

Portfolio Management also provides the organization an accurate and up to date mechanism to analyze services based on risk and return, evaluate how each service will enable the business to achieve its overall strategy and track the investment in each service throughout its entire lifecycle thus ensuring efficient and effective use of limited resources throughout the entire service lifecycle.


For more information on ITIL Service Strategy training and certification please go to http://www.itsmacademy.com/itil-ss/

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…