Skip to content
← Product management

SHIP / REQUIREMENTS & PRDS

Keep the purpose.
Define the work.

Turn product evidence into a specification the team can inspect. Carry the source, scope and acceptance criteria into the delivery conversation.

A complete Product workspace. Connect the wider work when useful.
Requirements & PRDs workflowSources → scope → acceptance. An authored illustration with fictional planning examples. RQ-184Customer needOne external reviewer POL-03The access ruleNamed and revocable SPEC-31 / DRAFTExternal-reviewsharingIN SCOPEOne reviewer. One item.ACCEPTANCE TO REVIEWNamed accessExplicit expiryOwner revocationPurpose stays attached CITED SCOPE. EXPLICIT BOUNDARIES.
Sources → scope → acceptance
Product workflow illustration · Fictional planning examples
01Cited requirements
02Explicit acceptance
03Controlled handoff

SEE THE WORK / MAKE A CHOICE

A clear scope.
A reviewable boundary.

Inspect the fictional specification, then choose how an external reviewer should gain and lose access.

Working demo screens · Fictional examples

PRODUCT / INSIDE THE DEMO

Keep the source inside the specification.

Inspect the problem, cited evidence, inclusions and exclusions. Resolve the access question before recording the release plan.

The problem, supporting sources and acceptance criteria travel together into release planning.

Try the specification reviewInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Inspect the problem, cited evidence, inclusions and exclusions. Resolve the access question before recording the release plan.

PRODUCT / INSIDE THE DEMO

Make acceptance specific.

Choose an external access model. The selected boundary becomes explicit acceptance criteria for the fictional plan.

Make the access rules explicit: who can review, how long they have and how access ends.

Try an acceptance decisionInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Choose an external access model. The selected boundary becomes explicit acceptance criteria for the fictional plan.
01

FRAME THE WORK

Start the specification with the problem.

Build a cited specification around the problem, evidence and goals, with non-goals, edge cases, metrics and rollout considerations. Stories and acceptance criteria make the intent checkable, and open questions stay visible instead of being answered by assumption.

Start with
Product evidence, an intended outcome and the proposed scope.
Work toward
A cited specification draft with stories and acceptance criteria.
Detail of the Product demo with fictional example data
ProcessScout / Producta cited source the specification uses · fictional data
02

PREPARE THE HANDOFF

Send the work with its explanation intact.

Prepare epic and story batches from a confirmed specification for Jira, Azure DevOps Services or GitHub, one tracker per Product. Credentials, field mappings and permissions come first, and incoming story text is proposed for review rather than overwriting the accepted specification.

Start with
A confirmed specification and a configured tracker connection.
Work toward
A prepared delivery batch and a reviewable path for incoming changes.

A handoff with its explanation

  1. Accepted specificationSPEC-31
  2. Handoff bundleSources and decisions
  3. Delivery teamReads the reason too
Illustration · fictional example

HARBOR / THE WORKED EXAMPLE

“Let an external reviewer in” becomes a checkable brief.

Harbor’s fictional PRD names the problem, includes the source request and defines the external reviewer’s access scope. Acceptance criteria cover permitted content, excluded areas and revoked access. The team can review those boundaries before preparing stories for its delivery tracker.

Walk through this example

A REQUEST BECOMES A CHECKABLE SCOPE.

  1. Source requestShare one deliverable
    RQ-184
  2. SpecificationExternal review sharing
    SPEC-31
  3. AcceptanceNamed reviewer, seven-day access
    3 CRITERIA
  4. HandoffStories for your tracker
    PREPARED
Fictional planning example · No result is claimed
03

CHOOSE A DELIVERY PATH

Add Build when the work and setup are ready.

For suitable software work, a permitted repository connects the Product to Build Factory (beta), which designs and builds automations ready to deploy. Factory adds its own preparation, scope, checks and approval; the Product keeps the reason attached, and your team deploys the result.

Start with
A scoped software change and, where needed, a permitted repository.
Work toward
A product brief ready for the chosen delivery workflow.
Detail of the Build Factory demo with fictional example data
ProcessScout / Build FactoryBeta · a scoped brief · fictional data

THE PRACTICAL DETAILS

From draft
to handoff.

Talk through your workflow
Can we use PRDs without Build Factory?

Yes. Product specifications and the product workflow have their own use. Build Factory is an optional connection for suitable software work and requires its own setup and permissions.

Will accepting a PRD create tickets automatically?

Specification acceptance and tracker push are separate operations. The confirmed specification can be used to prepare a batch; a configured connection, mappings and the appropriate authority are needed to send it.

Can external story edits overwrite the product decision?

Incoming story text is proposed for review. The confirmed specification and existing running or historical build membership are not silently rewritten by that incoming text.

YOUR NEXT PRODUCT DECISION

Draft one specification.
Hand it over intact.

Try a fictional example, or bring one question from your product.

Product view

ProcessScout interactive demo · Fictional Harbor data