1. Overview

The Rundoo Change Management Program (“Program”) outlines the procedures and controls for managing changes to Rundoo’s systems, applications, and infrastructure. The Program is designed to minimize disruption to operations, ensure the integrity of systems, and maintain security while facilitating necessary updates or modifications. This document serves as a guideline and is subject to change at Rundoo’s discretion.

2. Scope

This Program applies to all system changes, including but not limited to software updates, infrastructure modifications, and configuration changes, initiated by Rundoo’s internal teams or external service providers. All changes must be submitted through Rundoo’s technical system, GitHub, and require peer review before implementation. These guidelines aim to ensure effective change management but do not guarantee the prevention of all risks or disruptions.

3. Change Management Process

• Change Requests: All changes must be formally requested through Rundoo’s internal tracking system. Requests will be evaluated based on their potential impact on system performance, security, and business continuity.
• Impact Assessment: Each change will undergo an impact assessment to determine the risks and benefits associated with the modification. Rundoo does not warrant that all risks will be identified or mitigated.
• Peer Review: All changes, regardless of their size or significance, must be submitted through GitHub and undergo a peer review process. Changes are only approved after review and consensus from designated team members, though this process does not guarantee the absence of errors or issues.
• Approval Process: Significant changes must be reviewed and approved by the appropriate stakeholders, including IT and security teams. Emergency changes may bypass this step but will be documented and reviewed post-implementation.
• Testing and Validation: Where feasible, changes will be tested in a controlled environment before being deployed to production systems. Rundoo will make best efforts to ensure smooth deployments but does not guarantee that all issues will be identified in testing.
• Implementation: Approved changes will be implemented according to the designated schedule. Rundoo aims to minimize operational disruptions but cannot ensure that no interruptions or side effects will occur.
• Post-Change Review: After the implementation of significant changes, a review will be conducted to evaluate the success of the change and any lessons learned. This review does not provide assurances of future performance or risk prevention.

4. Emergency Changes

Emergency changes necessary to address critical vulnerabilities or operational failures may be implemented immediately without full adherence to the standard approval process. Rundoo will prioritize restoring operations but does not guarantee the prevention of adverse effects in such cases.

5. Program Modifications

Rundoo reserves the right to modify or update this Program at any time without notice, based on evolving operational needs or regulatory requirements. No specific security or operational performance guarantees are implied.

6. Disclaimer

This Change Management Program is intended as a general framework for managing changes within Rundoo’s systems. It does not create any contractual rights or obligations, nor does it guarantee specific results, system uptime, or security outcomes. Rundoo disclaims any liability for disruptions or issues arising from changes made under this Program.

https://embed.notionlytics.com/wt/ZXlKM2IzSnJjM0JoWTJWVWNtRmphMlZ5U1dRaU9pSkNZMlJNVm1seFdHUjViMmRYZERKbVlsQkpaaUlzSW5CaFoyVkpaQ0k2SWpFeU1HVXhNVE01T0RabFlUZ3dNemhoT1RRNVpqQXhNVE0yTldWa056ZGxJbjA9