• Table of contents

<aside>

• ‣ </aside>

Purpose

The purpose of this policy is to ensure that all changes to the company's SaaS platform are managed effectively, minimizing risks while maintaining agility. This policy provides guidelines for change request submission, evaluation, approval, implementation, and communication.

Scope

This policy applies to all changes affecting the Upmind platform, including but not limited to code changes, infrastructure updates, security patches and configuration adjustments. It covers all teams involved in the change process, including Product, frontend and backend development teams, platform and relevant stakeholders.

1. Roles and Responsibilities

• Sales:
  • Feeds requests from prospects, to Product.
  • Communicates client priorities and dependencies.
  • Communicates back to prospects with updates, and confirmation once changes have been made
• Product:
  • Moderates requests raised by clients via Featurebase.
  • Manages the backlog and prioritizes change requests.
  • Ensures proper scoping & refinement of tasks before they are assigned to development teams.
  • Approves or rejects change requests based on business value and impact.
  • Maintains an up-to-date roadmap which is visible to clients.
• Development (Frontend & Backend):
  • Participate in refinement & scoping sessions to ensure changes meet customer needs and are implemented with least possible risk to the platform.
  • Implement changes according to priority and backlog refinement.
  • Conduct testing to ensure the stability and security of the changes.
  • Collaborate with QA and stakeholders to validate changes.
• QA:
  • Reviews requirements to ensure they are adequate, before development.
  • Validates changes before deployment.
  • Conducts regression and performance testing to ensure minimal disruption.
• Platform:
  • Ensures infrastructure-related changes are properly reviewed and do not introduce service disruptions.
  • Assists in deployment and rollback planning.

2. Change Management Process

• As part of backlog refinement sessions, the change is reviewed for completeness and alignment with business objectives