Release Process

Roles / Responsibilities /
Processes

Created By:
Naveen Lohchab
Date Created: July 14, 2014

Project Release Analyst Roles / Responsibilities / Processes

Table of Contents
Document Purpose..................................................................................................... 3
Project Release Analyst.............................................................................................. 3
Role......................................................................................................................... 3
Responsibilities........................................................................................................ 3
Development Team..................................................................................................... 3
Responsibilities........................................................................................................ 3
Release Analyst Check List...................................................................................... 4
Configuration Changes............................................................................................ 5
Management Team..................................................................................................... 5

Page 2 of 5

Project Release Analyst Roles / Responsibilities / Processes

Document Purpose
The purpose of this document is to provide information on the updated
Release Process and who is responsible for each task.

Project Release Analyst

Role
The role of the Release Analyst on the RBR Project is to aid in the
implementation of one or more IT changes, upgrades, releases or
installations.

Responsibilities
-

To create, schedule and close Release Plans for releases to the UAT,
TRAINING and PROD organizations or for Infrastructure updates,
clean up tasks or disaster recovery tests. This will include setting up
the Release template folders.
To monitor any releases that occurs during regular business hours.
To answer Release questions and provide guidance when needed.
To assist, where possible, in getting emergency changes escalated.
To assist the ITD Project Manager in getting answers to questions
that needs to be defined.
Attend PMO meetings to provide information in relation to releases
whats ongoing, delayed, completed.
To move all Release components to the appropriate Backout folder
in the Release Plan locations.
To schedule and host Release Plan review meetings for UAT,
TRAINING and PROD.

Development Team
Responsibilities
-

To monitor any releases that occur outside of regular business

hours.
To conduct all QAT1 releases
To Track all Version and Build numbers.
To provide the Release Analyst with a list of Version and Build
numbers once the Project Schedule has been updated with the final
release dates for the next implementation.
To populate the Release folders with all required components
needed for each release solutions, configuration files, xml file,
SE.Web.Portal folder etc.
To create and execute the TFS queries and providing QA with the
Release Notes report.
Page 3 of 5

Project Release Analyst Roles / Responsibilities / Processes

-

To provide the Release Analyst with as much advanced notice as

possible when non-scheduled releases are required. This may
include situations where the team is anticipating an emergency
release to fix a Prod issue or possibly needing a quick release to
UAT before going to Production.

Release Analyst Check List

The Development Team is to provide the answers to the following questions
for every regularly scheduled Release.
*We need to improve the communication to be clearer and timelier and this
Check List may help.
1. What Version numbers are we using in QAT1, UAT, TRAINING and PROD?
Please provide this information no later than 1 week prior to the release.
2. What Build number will be used?
Please provide this information no later than 1 week prior to the release.
NOTE: A suggested plan for 1 and 2 above is, once the Release Dates
have been finalized; send the Release Analyst a spreadsheet that outlines
all of the Build and version numbers to be used in the upcoming releases.
3. Will a new XML file be provided?
4. Are there Data Imports?
5. Are there Manual Imports? (I believe this will no longer occur as Scribe
should handle all imports. However, I will leave this in as a check for now)
6. Are there any configuration changes that need to be applied? If so, the
please provide the proper documentation in the Release folder and notify
the Release Analyst so it may be incorporated in the Release Plan.
7. Will Ben / Ryan need temporary access during the release? Please advise
the Release Analyst on who will require the access.
8. Are there New Solutions being imported? If so, please advise Release
Analyst in advance of what the solution name will be and what order it
needs to be imported in.
9. Are there any Solutions being renamed? i.e. Wildlife Management to
Wildlife. If so, please advise the Release Analyst in advance of what the
solution name will be going forward.
NOTE: When communicating what solutions are being included in the
release, please use the actual solution name and not by another business
Page 4 of 5

Project Release Analyst Roles / Responsibilities / Processes

name. The Release Analyst will not recognize the solution by any other
name other than what is regularly used in the Solutions Release folder.
10.Are vendor solutions being imported during the release? i.e. solutions to
fix technical issues such as MicrosoftXrmCustomrePortal.zip. If so, please
advise the Release Analyst and provide the name and order of where it
needs to be imported.

Configuration Changes
All documentation for configuration changes need to be clear and specific.
Rochelle Joerissen will be our main resource for apply these changes in UAT,
TRAINING and PROD. If she is unavailable, Jonathan Lopez will be her backup.
Should both of these resources be unavailable, the assigned ISM resource on
the Release will be applying the changes.

Management Team
-

To schedule in release dates and add to the Project Schedule.

To notify the Release Analyst when the release dates are finalized.
To ensure that the Project Schedule accounts for keeping the
regions in sync.
Note: Mock Prod releases are no longer being done as it was felt
that this will be accomplished by releasing to the Training
Environment.

Page 5 of 5