Responsibilities: - Establishing milestone schedules,
- Individual, team, project, and organization communications,
- coordinating Dev, Test, Tech Ops, Product Owners and other stakeholders throughout the release process
- All of the release activities, activating offline stack, etc, are done by others - RMs don't do those things but plan and coordinate all of the efforts leading up to and following (prod validations)
Description: Industry standard release processes- RM responsibilities typically start with cargo/code freeze; when the code is ready to be installed in the staging environment (pre-prod). Mostly automated.
Example environments are Staging, Offline Stack, and Prod.
Examples:
Release to prod for Metro (prepaid brand) involves activating the Offline Stack and pulling out the current active stack.
Release to prod for TMO App involves a gradual increase in traffic to the new code (e.g.: 10% on day 1, 20% on day 2, etc.)
Releases can be a mix of planned (BAU) and unplanned. Timing is usually during the day but they sometimes run into the night. There can also be night deployments if dependencies require it.
Each of the T-MO properties we support, both web and phone based, usually have different dependencies, stakeholders, and needs/aspects (project specific)
Web apps used for bug and project tracking: Jira, Confluence, & Pier
Slack and WebEx are used for most team and project communications
Skills requirements: Good software release management or project management experience.
Strong knowledge of software release processes.
Exceptional written and verbal communication skills (top priority for the client)
Exceptional organization skills (top priority for the client)