Skip to main content

Service Acceptance Criteria

I have often been asked what value Service Acceptance Criteria (SAC) provides. The SAC's importance grows as organizations seek to validate and optimize service value. Do you want to increase value for your business and customers? First, let’s understand what SAC is.

What is Service Acceptance Criteria?

Service Acceptance Criteria is a set of criteria used to ensure that an IT service meets utility, warranty, and experience requirements. Other requirements may also be included, such as manageability and compliance.

Service Validation and SAC

The ‘Service Validation’ portion of the Service Validation and Testing practice ensures that SAC is defined, verified, and documented. Service Validation is performed in the earlier stages of the product and service lifecycle (ideation and design). It confirms that the proposed service design meets agreed service requirements and establishes acceptance criteria for the next stages (development, deployment, and release).

Service Validation also informs the scope and focus of testing activities. Product teams establish the criteria that need to be tested based on the agreed service or product requirements, the Service Design Package, and the organization’s quality standards.

Depending on the level of validation and testing (product, service, or component), the documented assessment criteria are agreed upon and approved by a relevant authority (typically a product owner, service owner, technology team lead, and, where relevant, a customer or representative).

During the ‘Testing’ portion of the Service Validation and Testing practice, test strategies and test plans are developed and implemented based on the criteria identified through Service Validation.

Following testing, a quality specialist reviews test records and reports to verify that the product, service, or component has been tested for the agreed acceptance criteria, and that the tests are valid and trustworthy. This verification may be required before deployment, release to users, or customer acceptance.

Continual Validation and Testing

In the past, SAC was sometimes considered only at the end of the value stream. Today, high-performing service providers apply Lean, Agile, and ITIL 4 methodologies that encourage iterative and incremental ways of working.

The Service Validation and Testing practice is not just about testing a ready-to-release product or service. These activities should be conducted throughout the entire product or service lifecycle. Organizations must continuously define and evolve the SAC throughout that lifecycle.

Validation and testing activities create important feedback loops, informing every step of the digital product lifecycle and ensuring the organization focuses on delivering real value.

Comments

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...