Define release scope
Group the issues that belong to a version and keep active and archived releases organized.
A release is more than a date on a roadmap. MMC PM makes releases first-class project records, keeping target dates, assigned work, notes, acceptance activity and development context visible as the team moves toward launch.
Group the issues that belong to a version and keep active and archived releases organized.
Review delivery status, target dates, UAT activity and unresolved work from the project workspace.
Maintain release notes and delivery evidence alongside the work that produced them.
Use connected delivery records instead of rebuilding the same project story across disconnected tools.
Create named releases with dates, status, notes and an explicit collection of delivery items.
Assign tasks and other work to a release directly from the delivery workflow.
Review the scope and state of a release without rebuilding it in a separate tracker.
Capture launch context and update notes as the release approaches readiness.
Keep acceptance activity close to the release and the work being validated.
Review connected commits, pull requests and deployments where project integrations are configured.
Create the release, target date, purpose and initial delivery scope.
Assign work from the backlog and track progress through the project workflow.
Coordinate testing and UAT while resolving remaining defects and approval items.
Finalize notes, confirm readiness and preserve the completed release record.
Product, engineering, QA and delivery leaders can work from the same release context, reducing the gap between what the roadmap promises and what the team is actually ready to ship.
Yes. Project delivery items can be linked to a release and reviewed from its detail view.
Yes. Release records include notes that can be maintained with the delivery scope.
Yes. Teams can separate active and archived releases while preserving their history.