Freddy at 17:06, 13 December 2018

2018-12-13T17:06:30Z

Freddy: Created page with " ==PURPOSE== To formalize the procedures and charges involved when customers request an off-cycle software release to be created for their enhancements to be made available b..."

2018-12-13T17:02:35Z

Created page with " ==PURPOSE== To formalize the procedures and charges involved when customers request an off-cycle software release to be created for their enhancements to be made available b..."

New page

==PURPOSE==

To formalize the procedures and charges involved when customers request an off-cycle software release to be created for their enhancements to be made available before the next scheduled software release. This procedure does not apply to hotfix requests related to software issues that affect the general release.

==APPLICABILITY ==

This applies to any request from a customer to make custom software developments available on a special release outside of the normal release timing.

==POLICY (The goal/expectation/standard to reinforce)==
#The Adjutant Desktop Monthly Release is made available to our customers on the 15th of every month. If the 15th falls on a Friday, or a weekend, the release date should be adjusted so that it doesn’t put our customers or our support teams in a difficult support position with a weekend or holiday release.
#*A release calendar will be circulated for the upcoming year, and will note the expected release date which takes in to account holidays and weekends.
#*The release calendar may be adjusted as needed, based on resource availability, or special situations.
#Customers may request that their ECR, or a group of ECRs that are ready for release be made available for immediate release. This request for a custom/off-cycle release is billable at three (3) hours of development time at the customer’s development rate.
#The consultant must inform the customer of the charge and get their understanding and approval before requesting the custom release.

==PROCEDURES (Steps/Action Items/Behaviors taken to meet expectations)==

#Create a task under the requesting customer’s customer number using the 4.36 Standard Task Code. Update the Task Note with the ECR(s) that need to be included on the custom release. Assign the task to David Blacklock.
#Development will build the custom release version with the ECRs specified and complete the ticket. The completed ticket will generate a notification email to all consultants similar to the standard hotfix notification.
#Once the release version has been created, the consultant should notify the customer that the release is available.
#The customer will be billed for 3 hours of development time once the task is routed through billing.

[[Category: SOP Guides]]
[[Category: Software Release]]

@@ Line 10: / Line 10: @@
 This applies to any request from a customer to make custom software developments available on a special release outside of the normal release timing.
 ==POLICY (The goal/expectation/standard to reinforce)==
-#The Adjutant Desktop Monthly Release is made available to our customers on the 15th of every month. If the 15th falls on a Friday, or a weekend, the release date should be adjusted so that it doesn’t put our customers or our support teams in a difficult support position with a weekend or holiday release.
 #*A release calendar will be circulated for the upcoming year, and will note the expected release date which takes in to account holidays and weekends.
 #*The release calendar may be adjusted as needed, based on resource availability, or special situations.
 #Customers may request that their ECR, or a group of ECRs that are ready for release be made available for immediate release.  This request for a custom/off-cycle release is billable at three (3) hours of development time at the customer’s development rate.
-#The consultant must inform the customer of the charge and get their understanding and approval before requesting the custom release.
+#The consultant must inform the customer of the charge and get their written approval (email is okay) before requesting the custom release.
@@ Line 21: / Line 24: @@
 ==PROCEDURES (Steps/Action Items/Behaviors taken to meet expectations)==
-#Create a task under the requesting customer’s customer number using the 4.36 Standard Task Code.  Update the Task Note with the ECR(s) that need to be included on the custom release.  Assign the task to David Blacklock.
+#Create a task under the requesting customer’s customer number using the '''4.36 Standard Task Code'''.  Update the Task Note with the ECR(s) that need to be included on the custom release.  Assign the task to David Blacklock.
 #Development will build the custom release version with the ECRs specified and complete the ticket. The completed ticket will generate a notification email to all consultants similar to the standard hotfix notification.
 #Once the release version has been created, the consultant should notify the customer that the release is available.

Off-Cycle Release Procedures - Revision history

Freddy at 17:06, 13 December 2018

Freddy: Created page with " ==PURPOSE== To formalize the procedures and charges involved when customers request an off-cycle software release to be created for their enhancements to be made available b..."