Skip to main content

Service Strategy and the Service Portfolio

Service Portfolio Management is a process that ensures that an organization has the right mix of services to meet business and customer requirements.  Strategists can use the service portfolio to evaluate offerings that are under consideration for investment and also to determine which services should be retired!  A complete history of people, process, technology and information from concept to end of life could be tracked via the service portfolio.  This investment framework is a valuable asset to every service provider.  The Service Portfolio and the activities performed in service portfolio management process serve as an overall basis for making strategic decisions regarding service offerings.  Major changes (those requiring executive approval) will be processed through the service portfolio management pipeline.  It is here that a proposal is defined, analyzed, approved and chartered before moving into service design and more importantly before moving to project management.  

Project Management and the Service Portfolio
A project is a temporary endeavor undertaken to create a unique product, service or result.  Project management applies resources to project activities to meet the project timelines, deliverables and budget requirements.  One could say that portfolio management sets the priority of the projects and ensures business alignment while project management oversees the individual project.  A project has a starting point and a stopping point.  A service on the other hand is ongoing and must be monitored and analyzed to ensure ongoing value and relevance.  Without executive analysis and prioritization and without the detailed tracking of information and knowledge via the service portfolio, businesses are at risk and projects could miss the mark when it comes alignment with strategic initiatives and business outcomes.

The Value of Service Portfolio Management
  • Ability to fuse IT provisions with strategic business initiatives and business outcomes.
  • Strategic insight into the impact that IT services have on the performance of the business
  • Improved productivity from staff and IT resources, through increased focus on services that offer the most value.
  • Lower cost (dear to the heart of business) can be achieved through the consolidation of duplicate services, enhancement of inefficient services, and retirement of services that no longer deliver value.
  • Relevant decisions are made relating to the creation, improvement, delivery, and retirement of services.
  • An enhanced ability to meet the dynamic business requirements and service demands.
  • Increased customer confidence (branding)  and reputation in the industry.
To learn more about creating and integrating your service portfolio and service catalog:


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…