These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Release Management
- Who it's for
- Software delivery teams
Software delivery teams
A software team groups work by project and release package. Developers and QA engineers use the task board while the delivery lead watches pending windows and triaged issues. The package is a planning unit for the next delivery conversation; actual deployment execution remains in the team’s chosen delivery system.
How Release Management is set up for you
Plan the release unit
Put the work to be delivered together in release packages under the right Projects record. Assign an owner and agree the planned dates before the team starts moving tasks.
Watch the exceptions
Use Open Issues and Blocked Tasks to find work that needs a decision. Issue triage records its outcome in operation receipts when the issue has severity and is still open.
Review hours
Team members submit time entries with a work date and project. The approval action records a decision and receipt for valid submitted hours.
Close the window
The window owner records Met or Missed after the planned date and keeps notes that explain the result. The delivery lead can check the package, issues and review evidence before reporting it.
A software team groups work by project and release package. Developers and QA engineers use the task board while the delivery lead watches pending windows and triaged issues. The package is a planning unit for the next delivery conversation; actual deployment execution remains in the team’s chosen delivery system.
Start with one active project, one package, a small task set and one pending deployment window. Agree which person maintains task status and who looks at issues before the window. Use a submitted time entry to rehearse the approval path, including a rejected attempt with nonpositive hours. Then review Operations Overview with the people who will run the weekly delivery meeting.
Before adding another project, check that package ownership, issue severity and window outcomes mean the same thing to each team. Keep a link to the execution system used for the actual deployment and decide where its evidence belongs. Review the [planning process](/release-management/processes/plan-and-deliver) and [window review](/release-management/processes/review-window) with a representative case.
Features to start with
Roles on the team
- Delivery Lead
- Owns the release plan, exception review and delivery handoff.
- Project Manager
- Maintains project schedules, package assignments and delivery risks.
- Developer
- Works assigned tasks and raises issues against a project.
- QA Engineer
- Checks issues and records review evidence for delivery work.
Set up Release Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.