Skip to content

Software Release Process

Objective

  • To have clear and comprehensive deployment plans.
  • Define Roles and Responsibilities during deployment.
  • Coordinate teams and resources within the organization.
  • Evaluate and Manage Risk.
  • Align Business/Stakeholders with Software Development (Features/Bug Fixes).
  • Introduce versions for the applications.

Types Of Releases

  • MVP Release / Bug Fix Release
  • Hotfix Release

Current Process

  • Teams perform code deployment as needed.
  • No formal or standard Process followed.
  • No status available in Jira.
  • A Ticket with status Complete does not indicate feature/bug is deployed in Production.

Cube Sprint Workflow

  • Introduce new Status ‘In Prod’.
  • Sprint Independent.
  • Complete Status will remove ticket from Sprint when Sprint is completed.

Release Process

Sprint Based (Option 1)

  • Detailed steps of the sprint-based process.

Monthly Release (Option 2)

  • Detailed steps of the monthly release process.

Deployment Process

  • As per Release Schedule meet on the last Wednesday of the month or Wednesday of Week 2 of Sprint 2.
  • Create a Filter/Search to identify Tickets with Complete Status.
  • Prioritize Tickets (code) that needs to be moved to Production.
  • Add tickets to Version.
  • Get Approval from Stakeholder PM, Project leader, Developers, and QA.
  • On the release day inform team members about the release and its impact on systems.
  • Once code is moved to Prod, QA should do regression test including the new changes (UAT if possible).
  • Send email to all team members notifying Version details and Features/Bug Fixes that were moved to Production.