On Thursday 28th October we are carrying out essential upgrades. The website may be unavailable for a period of time starting from 6am BST. We apologise for any inconvenience this may cause you.
Home > Case Studies & White Papers > Service acceptance criteria: Sometimes you got to be cruel to be kind

Service acceptance criteria: Sometimes you got to be cruel to be kind - White Paper

Julia Harrison

June 2017

All of our White Papers and Case Studies are subject to the following Terms of Use.

The goal of this article is to use the ITIL® Practitioner guiding principles “start where you are”, “collaborate” and “keep it simple”, to show how it is possible for IT service operations organizations that have not yet introduced DevOps practices to their service management to reach across the divide to software development to make improvements to their services.

To read the rest of this white paper and to get access to all white papers, please log in or create a user profile.

Log in Create user profile
Current rating: 3.6 (5 ratings)

Comments

2 Nov 2017 Caspar Miller
Alternate text
Provides a better understanding of the term SAC, and also gives a theoretical example of sorts.
A practical example from a real-world application/use of SAC in a deliverable would have made for even more value.
27 Nov 2017 David Boothroyd
Alternate text
Fine as a primer, but I would like to see it expanded to qualify as a white paper. The SAC is one of the fundamental building blocks of collaboration in siloed IT - with a little backing from senior management, it's existence and treatment can expose significant risks and encourage and more transparent lifecycle for services. It would be great to see that journey played out in this document.
You must log in to post a comment. Log in