PRODUCT / INSIDE THE DEMO
Record the intent clearly.
Name the release, choose a target window and retain the links to the customer request and specification.
The planned release connects a target window with the source request and agreed scope.
SHIP / RELEASES & ROLLOUT
Bring versions, launch plans and rollout into the product story. Keep planned work distinct from what your team confirms it delivered.
A complete Product workspace. Connect the wider work when useful.SEE THE WORK / MAKE A CHOICE
Record a manual release without a repository, then define the outcome you will return to after a real release.
Working demo screens · Fictional examplesPRODUCT / INSIDE THE DEMO
Name the release, choose a target window and retain the links to the customer request and specification.
The planned release connects a target window with the source request and agreed scope.
PRODUCT / INSIDE THE DEMO
Choose a measure, target, owner and collection method before claiming that the product change helped.
Baseline, actual outcome and realized value stay unknown until real evidence is recorded.
ESTABLISH THE RELEASE
Create a manual release with a name, an optional date and the arcs or epics it includes; no repository or commit is required. The record ties the release to its planned work, whether your engineers built it or Build Factory (beta) prepared it for your team to deploy.
PREPARE THE INTRODUCTION
Launch-plan and cohort-rollout views sit beside versions and the changelog, so the introduction lives with the work being released. Plan who sees the change and when to review it, and keep that plan distinct from deployment evidence and later usage data.
An introduction, not just a date
HARBOR / THE WORKED EXAMPLE
In the fictional Harbor example, the team plans a manual release for external-review sharing and identifies the work it would include. Deployment and outcome evidence are still pending. The planned release is an intentional next step, with no shipped change or customer result claimed.
Walk through this exampleA PLANNED RELEASE, WITH NOTHING CLAIMED.
FOLLOW THE DELIVERED CHANGE
Keep planned, manually confirmed and deployed releases as different records, so the changelog says only what the evidence supports. A build that Build Factory (beta) prepared can carry its review record and approved client-note text; your team deploys it and records that step. Then connect the release to outcome review.
No. A manual release can be recorded with its name, optional date and included arcs or epics. It does not require a repository or commit.
No. The release record and launch plan do not deploy software, and neither does Build Factory (beta): it designs and builds a reviewed change, ready to deploy, and your team deploys it through its own process.
A build that Build Factory (beta) prepared, that your team has deployed and recorded, with approved client-note text. A plan or an unconfirmed deployment should not be presented as the same evidence.
YOUR NEXT PRODUCT DECISION
Try a fictional example, or bring one question from your product.
Allow optional analytics to help us improve ProcessScout? Privacy notice