Skip to main content

Service Vs. Project

A question arose recently concerning the relationship between Service Management and Project Management. This is a topic of interest to many people since on the surface both approaches seem to be fighting for some of the same work space in organizations. When we go back to the basic definitions of each we can see that the two are not in conflict, rather are very complementary. However, the relationship may not be as many people expect. I have found that the relationship is one of time: short term bursts of creation activities (outputs) inside a larger ongoing management lifecycle (outcomes).

Let us start with the definition of service and service management (according to ITIL®):
Service: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks

Service management (SM): A set of specialized organizational capabilities for providing value to customers in the form of services. 
Both of these definitions imply a chain of activities coming together over time to provide an outcome to a customer. These are ongoing ideas that provide both short term and long term benefits to customers. Services are outcome not output based.

Now we will turn to the definition of project and project management (according to PMBOK®):
Project: A temporary endeavor undertaken to create a unique product, service or result.
Project management: The application of knowledge, skills and techniques to execute projects effectively and efficiently.
These terms imply defined time frames with unique outputs delivered at the end of the time frame. This includes the creation not just software, but services, infrastructure, process, organization and just about any other output. Projects are output not outcome based.
When we put these ideas together we can recognize that a project is a method by which we design and transition a service into existence. Projects are defined bursts of activity (including the development, building, testing and delivery) that result in the creation of services that bring value to the customer. Thus project management is the short term control and guidance of projects that result in long term value-laden services. Once a project completes its objective or goal of creating a service, then the project closes until we need to do the next burst of creation. When a project closes, then the activities associated with project management will end as well.
Since services are lifecycle (repeatable and long term) in nature, service management is an ongoing lifecycle based approach to strategizing, designing, transitioning, operating and improving services to ensure long term, consistent and ongoing value to the customer. Service Management looks not just at the creation aspect of a service, but the entire lifecycle: conception, creation, growth, maturity and even retirement.
By seeing that project work and the discipline of project management resides as one of the many methods that come together inside the overall lifecycle of a service to create value for customers, we find that service management and project management work very well together.

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

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th