4388 – Software Release Coordinator

The Software Release Coordinator will work with the Project Team. This team includes, but is not limited to, Product Owners (POs), Project Manager (PMs), Development Lead, Business System Analysts (BSAs), QA Program Test Coordinator, and QA Test Analyst. This role will work to understand the prioritized backlog of work, the scope of the planned work packages, and help coordinate and usher the pre-defined work packages through the Software Development Life Cycle (SDLC) phases; making sure that the correct processes are followed as the work is assigned and executed. The Development Technical Lead and the Release Coordinator will identify the Construction Phase work breakdown tasks by following the SDLC processes.

Software Release Coordinator works with the client Managers and Project Manager and to confirm that the Release Management process and Requirement Management plan is followed. The Release Coordinator works with the Project BSAs, the Project PM, and the QA Test Analyst to confirm that all release deliverables (entry/exit criteria) have been completed in-line with the Project Schedule and according to project governance. Release coordinator provides release notes, required approvals and relevant communications to the Project PM. Release coordinator attends project-team daily standups and provides release updates to the Project Team. The Release Coordinator communicates to the Project Manager any risk and issues with potential to impact project scope, schedule or budget. The Release Coordinator works with the client Manager, development team and Project Managers to identify alternatives and adjust plans to deliver as originally planned.

Release Coordinator will have a background in SW Release Management with experience in facilitating daily developer’s stand-up meetings and utilize Atlassian’s Jira to manage team development tasks, bug and issues tracking.

Job Tasks:
Elaboration Phase
– Works with Project Team to monitor and track the construction progress of pre-defined Work Packages. (See the Requirements Management plan for details on how the scope of Work Packages are defined)
– Helps to develop and refine the project schedule by giving input to the project team during schedule development activities.
– Helps communicate schedule expectations between the Project Manager and development team members.
– Communicates and/or escalates resource needs or constraints, to Program and Project Managers, and client Managers, in order to accomplish the tasks and activities as identified in the Work Breakdown Structure.

Construction Phase
– Work alongside the Development Lead and the BSA Lead to utilize Agile principles in iteration/work package -planning meetings to plan, capture, assign, and track development tasks in Jira.
– Plan and report Sprint progress
– Time/story points tracking
– Workload reports
– Monitors Jira to report on defects and issues reported during the Construction Phase.
– Monitor Jira data to ensure correct records are being updated or created according to the Jira governance guidelines.
– Coordinates with other project team members for timing of releases and moves to UAT; as necessary.
– Facilitate the Change Control Process by coordinating releases with multiple project teams and IT sections and integrating bug fixes into UT and UAT code-lines and version management process working with development teams and DevOps.
– Monitors and tracks the Construction and Transition Phases to communicate approved changes and defect fixes.
– Facilitates developer’s standup meetings and addresses roadblocks.
– Participates in the Project stand-up meetings and communicates Development progress and roadblocks.
– Escalates any development concerns or issues to client Managers and Technical Leads.
– Provide the Program and Project Managers, client Managers, and Technical Leads updates through the Weekly Status Report(s). Reported information shall include:
– Development concerns and issues from Jira
– Deviations or expected deviations from the development schedule
– Development plans for the following week
– Requested changes to the defined project scope.
– Construction (BFT-Phase) defects reported from Jira

User Testing Phase (UT)**
**This phase is similar to UAT, in that, as one body of work is completed, information shall be added to the appropriate documents and reported similarly, but there is not a formal Transition Phase with approval to release into production.
– Reviews Turn Over Reports (TOR) for Construction Phase Iteration completion.
– Monitors and plans for defects classified as must-fix for the release or have future-work dependencies.

Transition Phase (QA Acceptance/UAT Process)
– Reviews Final Turn Over Reports (TOR) for completion, and creates and sends the “Construction Completion Report” (CCR) and to Quality Assurance to start the QA Acceptance Process and copies the Project Manager.
– Coordinates with Product Owners, QA Test Analyst, BSA Lead, and development team to resolve defects classified as must fix for the release.
– Ensures defects are managed, tested and records defects resolved in the “TRANSITION – jClarety UAT Build Report” submits the report to the QA Test Analyst and Project Manager.
– Coordinates the Deployment Release Process and desired deployment dates with the Production Change Management Team.

Contract Deliverables:
– Monthly Contractor Support/Task Log.
– Monthly Release Management Report to EAS, Program, and Project Managers.
Report shall include the following;
– Development sprints/tasks completed for the month.
– Development plans for the following month.
– Report on any requested changes to the defined project scope.
– Report on Construction Process defects/issues reported (data to be kept in Jira). Include issue analysis reports such as resolution time, average age, etc.
– Provides Metrics (from Jira) on Release, Epic, Development work/task velocity, and Defect burn down rates.
– Completed Construction Completion and Turn Over Reports per Work Package to the QA Acceptance Process utilizing client templates.
– Completed Release Notes upon Quality Gate approval to release into production.