Skip to main content

Service Acceptance Criteria

I have often been asked what value does the Service Acceptance Criteria (SAC) provide?

First let’s understand what the SAC is by definition.

Service Acceptance Criteria: A set of criteria used to ensure that an IT Service meets its functionality and quality requirements and that the IT Service Provider is ready to operate the new IT Service when it has been deployed. This set of criteria is in the form of a formal agreement that an IT Service, Process, Plan or other deliverable is complete, accurate, reliable and meets the specified requirements.

We must understand that all design activities are triggered by changes in business needs or service improvements. In order to design and deliver IT services that meet the changing needs of the customers and the business, we must ensure that the contents of the Service Acceptance Criteria are incorporated and the required achievements are planned into the initial design.

The Service Acceptance Criteria is the document that will ensure the Service Provider is ready to deliver the new service by answering the following criteria:
  • Has the go live date been agreed to with all parties?
  • Has the deployment project and schedule been agreed to and made public to all stakeholders?
  • Have all SLR/SLA’s been reviewed, revised and agreed to with all stakeholders?
  • Has the Service Catalogue/Portfolio been updated and all appropriate relationships established within the Configuration Management System?
  • Have all users been identified/approved and appropriate accounts created for them?
  • Can all SLR/SLA targets be monitored, measured, reported and reviewed?
  • Can performance and capacity targets be measured and incorporated into the Capacity Plan?
  • Have incident and problem categories and processes been reviewed and revised for the new service?
  • Has appropriate technical support documentation been provided and accepted by Incident, Problem and all IT support teams?
  • Have all users been trained and user documentation been supplied and accepted?
  • Have appropriate business managers signed off acceptance of the new service?
With this documented criteria in hand we can insure that the Service Provider will meet the agreed needs of the customer and the business. It will insure that availability, capacity, security and continuity can be assured and thereby deliver value to the business.







Comments

Manuel said…
Who its responsible?
The Service Design Manager or process owner for Design Coordination would be responsible.

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 …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility