Release Management

Release management handled by Information Technology Services integrates the necessary planning, scheduling, controlling, and deploying of new software application and information system versions, releases, and patches and the transition from configuration, testing, to production environments as necessary in order to maintain a secure and fully supported technological infrastructure. We work with our colleagues within administrative offices and academic departments to plan and coordinate pre-release testing in order to maintain quality standards and minimize the risk of any disruption associated with updates and upgrades.

The Release Management service is available to all staff and faculty within Framingham State University who manage or utilize software applications and information systems that are under the centralized administration of the Information Technology Services (ITS) organization. This includes administrators, academic staff, research personnel, library staff, and any other roles that require the use of these software applications or information systems for daily operations. For instance, if the Business Office wants to take advantage of a newer release of the Banner Finance module then the appropriate person within that administrative department can initiate a request to upgrade that particular portion of the information system. Otherwise, ITS initiates how and when updates, patches and new releases are introduced into “production” in consultation with the cross functional administrative and student information management team and as part of the change management process administered by ITS.

Release Management offers several features and benefits to optimize the deployment and use of IT systems across the university.

• Standardized Deployment Procedures: By following an established set of protocols for each release, we minimize risk and ensure reliable, consistent results.
• Coordinated Scheduling: Our team ensures that software releases occur during prearranged times to minimize disruptions to users.
• Quality Assurance: Rigorous testing procedures ensure each release meets high-quality standards and functions as expected in the live environment.
• Detailed Documentation: Comprehensive records of each release facilitate better understanding, provide an audit trail, and allow easier troubleshooting.
• Risk Management: We identify, assess, and manage potential risks associated with each release, mitigating potential impacts on users and systems.
• Improved Communication: Release schedules and status updates are communicated effectively to all relevant stakeholders, ensuring transparency and setting expectations.
• Post-release Support: Our team provides robust support following each release, addressing any issues or concerns.

These features enable a smooth, seamless transition of software from development to deployment, enhancing the functionality and reliability of IT systems, and ultimately improving the effectiveness and productivity of all users across the campus.

To utilize the Release Management service at Framingham State University, the following prerequisites must be met:

• Eligibility: The individual or department requesting the service must be an authorized staff member, faculty, or student worker of the university.
• Software or Application: The software or application for which the release management is required should be a part of the university's IT systems or approved third-party applications.
• Compliance: The software or application release must comply with the university's IT policies, privacy, security, and legal regulations.
• Request Submission: A formal request for release management service must be submitted via the procedure provided by ITS.
• Planning and Scheduling: The request must be placed in advance allowing sufficient time for planning, testing, and deployment in line with the university's release schedule. (Unless of course it is part of an approved emergency change request).
• Stakeholder Approval: For major changes or releases, approval might be required from relevant stakeholders or management.

To request this service fill out the form that can be accessed by clicking on “Request Assistance” from this web page and provide all required information in the form, including your contact details, details about the software or application, the desired date for the release, and any other specific requirements or details about the update or new release. Then click 'Submit' to send your request to the IT Service team. After your request is submitted, a member of ITS will contact you within a specified timeframe to discuss your request in further detail, plan the release, and provide you with an estimated schedule. Please remember to submit your request well in advance of your desired release date to allow ample time for planning, testing, and deployment.

N/A

At Framingham State University, we strive to provide prompt and efficient Release Management services. Here are our target timeframes:

• Initial Response: You should expect an initial response to your request within 1-2 business days. During this initial response, we will gather additional information if needed and outline the next steps.
• Planning and Scheduling: For standard releases, the planning and scheduling phase typically takes 5-7 business days. However, for more complex or large-scale releases, this process may take up to 15-20 business days.
• Testing and Validation: The time required for this step is highly dependent on the complexity of the release. Minor releases typically require 3-5 business days for testing, while major releases may need up to 10-15 business days or more.
• Deployment: The deployment itself is usually scheduled outside of peak usage hours to minimize disruption and typically takes 1-3 business days to complete.
• Post-Release Support: Support will be available immediately after the release.

Please note these timeframes are target estimates and actual times may vary depending on the specific circumstances of each request. It's also important to note that some stages may run concurrently, such as planning and testing, and that timeframes may be affected by factors outside the control of ITS, such as vendor response times or system compatibility issues.