Our Kids of Miami-Dade/Monroe, Inc. 1 of 7 OK OP Effective Date: April 30, 2014

Transcription

1 Our Kids of Miami-Dade/Monroe, Inc. 1 of 7 Our Kids Information Technology Department Programming Change to Production I. Policy/Purpose: This procedure defines the process for programming changes to the OK production environment from initiation through promotion to production. The intent is to insure integrity, quality and security of the OK production environment. This procedure addresses all programming changes to the OK Production environment ranging from a new application, report or database to modifications to existing applications, reports or databases. II. III. IV. Scope/Responsibility: This procedure is strictly limited to those systems managed by the Application team. This procedure DOES NOT apply to the Solomon financial system, which is managed by the Finance Department. Location: This policy and procedure can be located on the Our Kids Intranet site at Definitions: Programming Changes: Any changes made to the OK Production Environment ranging from a new application, database or report to a modification of existing applications, databases or reports. Production Environment: All computing resources used to record, track, and manage the OK business that is currently managed by the Application team: SharePoint CSIS/ASK Safe Haven Promotion to Production: The process of verifying the integrity, quality and security of items planned for integration into the Production Environment which includes recording the changes.

2 Our Kids of Miami-Dade/Monroe, Inc. 2 of 7 V. Procedures/Process: Business Analysts define business requirements and assess the need for computing environment changes. If need is found, determine: 1. Overview A. New application, reports, database required 1. In House 2. Integration of Third Party product or Third Party product a. Hosted remotely b. Hosted internally B. Changes to existing application, reports, and databases required 1. In House a. Canned application b. Custom application 2. External a. Hosted remotely b. Hosted internally 2. New Application, Report, Database In House A. Business Analysts - Using Business Requirements, define the application requirements and specifications on the Change Request Form. B. Business Analysts - Review with Business Department to insure requirements are captured accurately. Obtain Business Department Manager Approval. Obtain approval from the Change Advisory Board (CAB). (See OK OP No IT Change Management Policy) C. Business Analysts - Submit to SDE D. Business Analysts - Conduct review session with Application, Network/Security, Help Desk as applicable to insure all impacts to OK Production Environment are identified and addressed within guidelines established. 1. New Application (application, DB, Reports) include all 2. New Report within established application Application E. Application Assess Effort, Define Estimated Delivery Date, Assign task to Developer in SDE 1. will be done in Environment 2. Move to and pre-test in Test Environment 3. Complete technical documentation

3 Our Kids of Miami-Dade/Monroe, Inc. 3 of 7 F. Application Notify Business Analysts when development, documentation and testing is complete and ready for Testing via SDE 1. Conduct review session with Business Analysts 2. Provide technical documentation G. Business Analysts Prepare User Documentation and Perform User Acceptance Testing with Business Departments in Test Environment 1. If testing failures are found, provide description and documentation of failures to Application for remediation. 2. If testing meets requirements, obtain Business Department manager approval signature and notify Application via SDE 3. Conduct Help Desk Training as applicable a. User Access adds, changes, terminations b. Login procedures c. Over view of application d. Support contacts and escalation H. Application Enter request for Promotion to Production in SDE. 1. Identify name and location of all items that need to be moved into production environment. 2. Attach technical documentation, if necessary 3. Identify impacts to Production Environment, if any 4. Identify move instructions and sequences 5. Identify Rollback plan 6. Add components to the code managements tool TFS I. IT Infrastructure review request for Promotion to Production 1. Check for impacts that deviate from original approved request. 2. Review Rollback plan 3. Assign implementation date/time 4. Establish notification and approval chain a. Approval Help Desk, Application, Business Analysts, CIO b. Notifications Business Areas and IT Management

4 Our Kids of Miami-Dade/Monroe, Inc. 4 of 7 J. IT Infrastructure complete promotion to production 1. If successful, notify IT Management 2. If there is a failure, implement Rollback plan, notify IT Management and Business Areas 3. New Application, Report, Database External A. Business Analysts - Using Business Requirements, define the application requirements and specifications on Change Request Form (See OK OP Change Management Policy and Attachment A) B. Business Analysts - Review with Business Department to insure requirements are captured accurately. Obtain Business Department Manager Approval. Submit for approval to CAB. C. Business Analysts Upon approval, submit to Vendor D. Business Analysts - Conduct review session with Vendor, Application, Network/Security, Help Desk to insure all impacts to OK Production Environment are identified and addressed within guidelines established. E. Vendor Assign Developer, Assess Effort, Assign Estimated Delivery Date 1. will be done in Environment 2. Move to and pre-test in Test Environment 3. Complete user and technical documentation F. Vendor Notify Business Analysts when development, documentation and testing is complete and ready for User Acceptance Testing 1. Conduct review session with Business Analysts, IT Infrastructure, Application, IT Help Desk 2. Provide user and technical documentation G. Business Analysts Perform User Acceptance Testing with Business Departments in Test Environment 1. If testing failures are found, provide description and documentation of failures to Vendor for remediation. 2. If testing meets requirements, obtain Business Department manager approval signature and notify Business Analysts 3. Conduct Help Desk Training as applicable a. User Access adds, changes, terminations b. Login procedures c. Over view of application

5 Our Kids of Miami-Dade/Monroe, Inc. 5 of 7 d. Support contacts and escalation H. Business Analysts Enter request for Promotion to Production in SDE. 1. Identify name and location of all items that need to be moved into production environment. 2. Attach technical documentation 3. Identify impacts to Production Environment. 4. Identify more instructions and sequences 5. Identify Rollback plan I. IT Infrastructure review request for Promotion to Production 1. Check for impacts that deviate from original approved Change Request Form.. 2. Review Rollback plan 3. Assign implementation date/time 4. Establish notification and approval chain a. Approval Help Desk, Application, Business Analysts, CIO b. Notifications Business Areas and IT Management J. IT Infrastructure/Vendor complete Promotion to Production 1. If successful, notify IT Management 2. If there is a failure, implement Rollback plan, notify IT Management and Business Areas 4. Changes to Existing Applications, DB s Reports In House A. Business Analysts - Using Business Requirements, define the application requirements and specifications on Change Request Form. B. Business Analysts - Review with Business Department to insure requirements are captured accurately. Obtain Business Department Manager Approval. Obtain CAB approval. C. Business Analysts - Submit to Application via SDE D. Business Analysts - Conduct review session with Application, Network/Security, Help Desk as applicable to insure all impacts to OK Production Environment are identified and addressed within guidelines established. 1. Significant Change to Application (application, DB, Reports) include all

6 Our Kids of Miami-Dade/Monroe, Inc. 6 of 7 2. New Report within established application Application 3. Minor Change to existing Report or Application Application E. Application Assess Effort, Define Estimated Delivery Date, Assign task to Developer in SDE 1. will be done in Environment 2. Move to and pre-test in Test Environment 3. Complete/Revise technical documentation F. Application Notify Business Analysts when development, documentation and testing is complete and ready for User Acceptance Testing via SDE 1. Conduct review session with Business Analysts 2. Provide technical documentation G. Business Analysts Prepare User Documentation and Perform User Acceptance Testing with Business Departments in Test Environment 1. If testing failures are found, provide description and documentation of failures to Application for remediation. 2. If testing meets requirements, obtain Business Department manager approval signature and notify Application via SDE 3. Conduct Help Desk Training as applicable a. User Access adds, changes, terminations b. Login procedures c. Over view of application d. Support contacts and escalation H. Application Enter request for Promotion to Production in SDE. 1. Identify name and location of all items that need to be moved into production environment. 2. Attach technical documentation e. Identify impacts to Production Environment. 3. Identify move instructions and sequences 4. Identify Rollback plan 5. Enter components in code control tool TFS I. IT Infrastructure review request for Promotion to Production 2. Check for impacts that deviate from original approved Change Request Form. 3. Review Rollback plan

7 Our Kids of Miami-Dade/Monroe, Inc. 7 of 7 4. Assign implementation date/time 5. Establish notification and approval chain a. Approval Help Desk, Application, Business Analysts, CIO b. Notifications Business Areas and IT Management J. IT Infrastructure complete promotion to production 1. If successful, notify IT Management 2. If there is a failure, implement Rollback plan, notify IT Management and Business Areas VI. VII. VIII. Cross Reference/Research Note: OK OP Change Management Policy OK OP System Management Information Resource Requests History of Revisions: Date created: February 10, 2009 Date(s) revised: February 27, 2012; April 14, 2014 Attachments/Forms: N/A