Standard Production Support Delivery Principles

Standard Production Support Delivery Principles

[su_heading size=”20″]Standard Production Support Delivery Principles[/su_heading]

We often work on large & complex operations spanning across various technologies and supporting various regions like US UK Asia and many more depending upon your organization ongoing projects.  It has been always hot cake in top management how to improve service delivery to optimum level to avoid any penalties in ongoing projects in case of any failures due to any reason or due to human error or it may be due to negligence .So question comes how to streamline service delivery.

There is no such hard and fast rule which we can implement which makes our services delivery perfect and life very much easier.Various minds have various views to tackle service deliveries and there are many theories and standards also in practice with many overheads.It is something similar like same problem can be solved using different method.We can make it kind of simple approach to make service delivery efficient by keep it simple stupid (KISS).

So, it is really important to ensure that we and our team follows standard delivery principles all the times to ensure that our clients and their business is least or not at all impacted due to simple human mistakes & improper kind of planning.  

According to my understanding we need to adopt below in our practice to minimize the possibilities of errors in service delivery.  

  1. DO NOT perform any changes in PRODUCTION environment during business hours. (Exception to this only is if approved by client explicitly and have been told to implement. )
  2. DO NOT perform changes either to project or business as usual without clear Implementation Plan & Recovery Plan or called Restore Plan or Backup Plan means how you can restore services if proposed change not went well.   
  3. Always keep management updated about any deviation in action plan , any issue in back-out if change not went well. If change is getting extended beyond approved hour, go for extended window approval if change exceeds window as it is also considered as incomplete change or failed change . 
  4. Any human error immediately inform your supervisor or manager and if describe impact if any. 
  5. Keep your focus on recovery /restoration of the service on top priority compared to  investigate root cause of the issue in case of any major incident.
  6. For all changes to servers you must have either incident or request to do so.Please adhere client methods without fail.Learn to say NO in absence of incident or approved request.  
  7. Try to develop SOP for all frequent change request which will help entire support infrastructure .Make checklist of activities and validate it during the process of implementations .
  8. Keep All Incidents, requests updated in timely manner with required details in case of any dependency why it is still open like H/W dependency or dependency due to some other team activity.
  9. Never sharing credentials/passwords as these represents individuality. Accountability is associated with it.

This is matter of discussion and endless kind of topic so it is better i will close this out  but if you bring above mentioned items into your practice during your support hour you will definitely reduce the chances of human error and can improve your service delivery.

[su_button url=”” target=”blank” size=”8″ wide=”yes” center=”yes” icon=”icon: facebook-square”]JOIN OUR FACEBOOK GROUP[/su_button]

RSY Digital World

RSY Digital World Founder & [email protected] Digital World. A UNIX Linux expert having a more than 20 years of experience in Solaris Red Hat Linux HP-UX AIX Unixware Open Server Veritas Storage Cloud Bigdata and many more in UNIX LINUX Infrastructure technologies.

Leave a Reply