1. Release Management
  2. Features
  3. Release planning
Feature · Release planning

Release planning

Plan releasable work under a project, with an owner and effort estimate.

OverviewMy projects
Release Management · Release planning

My projects

Projects

New
Project codeProject nameOrganizationEnd dateStatusOwner
PC-725Project 772ORG-763910 OctPlanned
PC-331Project 583ORG-342810 OctActive
PC-159Project 680ORG-401025 OctAt risk
PC-895Project 389ORG-212017 OctCompleted
PC-348Project 888ORG-633803 OctPlanned
6 of 6 records
PC-725Projects · PRJ-37109
Planned
Project nameProject 772
OrganizationORG-7639
End date10 Oct
Example screen with sample data

What you can do

Release planning in daily work

A project manager opens a project for an organization and records its dates and delivery method. The delivery lead creates a release package beneath it, names the owner, and estimates the effort. The package holds the work that the team expects to deliver together. Its status follows the work from not started to in progress, Blocked or Done. This keeps the release unit distinct from the overall project: a project may be active while one package needs a decision.

How the work is organized

  • Owner. Delivery Lead owns the package plan and its dates. Project Manager maintains the parent project and assigns task work. The package must point to the right project before the team uses its task effort and remaining hours in a release review.
  • Record. A package can be Blocked while its project remains Active. Compare the package end date and estimate with its assigned tasks, then decide whether to change scope, owner or date. Record that change on the package so the next review uses the same plan.
  • Decision. Confirm the package’s project, owner and task effort before the delivery lead changes its plan.

What to agree during setup

Agree which project owns each package, who can change package dates, and how the team uses the Blocked state. Review the project budget and the package estimate in the same meeting. The package effort figures draw on its tasks, so assign tasks to the correct package before using variance as a planning signal.

Rehearse this module with an active project and a package whose dates the team can discuss. Give each participant access to the linked records they need, then ask a second person to find the same owner, status and next action. Keep the original record available for the next review.

Check the handoff on an actual case

Follow a package whose owner changes while delivery is underway. Check that the project remains the same, the task list still represents the intended work, and the end date is still credible. If a defect appears, record it against the project; the lead can examine the issue beside the package before changing the release plan.

If the owner changes, the project manager checks the assigned tasks and their due dates under that package. The delivery lead can then decide whether its end date and effort estimate still reflect the work.

What your team sees

  • Release packages in delivery — See packages that have not started, are in progress or are blocked.
  • Active Projects — Check the parent project status, dates and owner before changing the package.

Follow the work through

See plan and delivery, issue triage and release window review for the steps around this work.

What it keeps track of

Data model
Projects
Engagements delivered for an organization, with budget and schedule.
Release packages
Release packages under delivery: the releasable unit of work with its schedule, effort, status and owner.
Organizations
Client and internal business organizations that projects are delivered for.
Team members
Delivery staff with role, practice and weekly capacity.

Who uses it

Permissions
Delivery Lead
, Project Manager and Admin.

Set up Release Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started