ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
Site Help
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Software Release Manager Job Description
Quick Summary
Describes typical duties for a Software Release Manager. This person essentially acts as a "program manager" of a set of projects slated to come together in the release of a software system.
What this is
Description of typical duties for a Software Release Manager - a person who acts as a "program manager" of a set of projects slated to come together in the release of a software system The SRM's primary responsibility is to ensure that the various component projects of a particular software release meet customer needs and are brought together and released on time with high quality, and the overall release reflects the best choices amount scope, costs, and time for the company.
Why it's useful
Software releases that involve multiple projects are complex undertakings. Interdependent projects must be coordinated. Decisions must be made at the release level as to the set of projects to be included, and the scope of those projects, based on available resources and customer needs, and individual projects' tradeoffs. The work on each project must be brought together into a coherent working software system with appropriate testing and documentation. The SRM's primary responsibility is to ensure that the various component projects of a particular software release meet customer needs and are brought together and released on time with high quality, and the overall release reflects the best choices amount scope, costs, and time for the company.
How to use it
Ideally, appoint a software release manager in the early days of release planning. Use this job description to consider the best person for this job. Often it will be a well-respected project manager with enough functional experience to understand the components of the release and how their technical complexity will affect the release schedule and risks. The software release manager will generally also have a software architect on the release team to be the primary expert on interdependencies and integration issues among projects in the release. (See also our related templates: Software Release Team Member Glossary and the Software Release Process Overview.)
If it is not practical to decide upon and appoint the release manager in the earliest days of release planning, then set a target date by which enough will be known about the release's components to determine and appoint the most appropriate person. See also our Software Release Process Overview for suggested "phases" of a software release including release definition and planning activities in the early phases.
This document provides guidelines for
- Overall management responsibility of the SRM
- Responsibility for early release definition and scope negotiation
- Responsibility for scheduling, tracking and control
- Responsibility for other aspects of release oversight
- Responsibility for process aspects of individual projects
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy