I have been asked this question several times before and I
actually blogged about it in 2011 (http://www.itsmprofessor.net/2011/08/service-design-package-sdp.html).
This is a tricky question because the SDP is merely a package of documentation
that tells the “story” of a service, from concept to testing to deployment and
beyond. The documentation can take many forms, from documents, records, source code comments, electronic media
Each organization and each service will have different criteria, looks and feels to their SDP. Apprendix A of the Service Design publication provides insight into the type of information that should/could go into the SDP. My best advice is to avoid reinventing the wheel – leverage documentation that already exists (e.g., requirements documents) and capture information at the point where it is being determined or distributed. Leverage the concept of the SDP as a vehicle for gathering better and more complete documentation. Decide on a repository – whether it’s a sharepoint/cloud folder or a formal entry in a Configuration Management System.
Each organization and each service will have different criteria, looks and feels to their SDP. Apprendix A of the Service Design publication provides insight into the type of information that should/could go into the SDP. My best advice is to avoid reinventing the wheel – leverage documentation that already exists (e.g., requirements documents) and capture information at the point where it is being determined or distributed. Leverage the concept of the SDP as a vehicle for gathering better and more complete documentation. Decide on a repository – whether it’s a sharepoint/cloud folder or a formal entry in a Configuration Management System.
Comments