Skip to content

Product manager guide

As a Product Manager you watch delivery across your apps, spot roadmap drift early, and give product sign-off before an admin promotes a release to Production.

Your workspace is the Product Release Workspace at /app/product-manager. It covers only the apps your admin has given you access to.

Card Meaning
Roadmap % Overall roadmap progress across your apps.
Release Health Average health score across release versions.
Sprint Complete % Share of sprint scope completed.
Scope Creep % How much sprint scope changed after the sprint started.
Dependency Risk Pressure from unresolved dependencies.
Tab Contents
Portfolio App Portfolio cards (status, progress, active, blocked, overdue and critical items, release health per app), Priority Distribution, App Progress, Release Health, Release Confidence and Dependency Risks.
Roadmap Roadmap Timeline (milestones and releases by target date), Milestone Progress, Milestone Risk, Sprint Velocity, Sprint Burnup, Sprint Burndown, Scope Creep and Roadmap Risks.
Release Release Health, Dependency Risk, Release Bottlenecks, and the release board.
  1. Portfolio: check which apps have blocked, overdue or critical items.
  2. Roadmap: compare milestone progress and risk with target dates; check burndown for the current sprint.
  3. Release: work through release candidates waiting for product approval.
  1. Open Release and scroll to the release board.
  2. Filter candidates by entity type, readiness, approval type or status, release version, approval gaps, due state or release state.
  3. Select a candidate. You’ll see:
    • Readiness: score, status, missing approvals, failed QA, blocked items, overdue items, dependency gaps and production risk.
    • Approval checklist: every approval the item needs and its status.
    • Approval history: who approved or rejected what, and when.
    • Collaboration: activity timeline, status history and comments.

You can decide Product Manager Approved approvals on items that are Ready to Ship or in Production. By default modules, submodules and apps need it.

The quickest way is the Waiting on you list at the top of Release (the tab badge shows how many): select Approve, or Reject, enter a reason and select Confirm rejection. Review opens the item on the board.

From the board:

  1. Select the release candidate.
  2. In the approval checklist, find Product Manager Approved.
  3. Select Approve, or enter a reason and select Reject. A rejection always needs a reason.

The readiness score recalculates immediately. When nothing is missing, the board tells you approvals are clear and an admin can promote the release.

Use the comments panel on a release candidate. Mention someone with @ and their name or email handle to notify them. See Comments and mentions.

  • Link tasks to milestones and sprints (admins set these on each task) or roadmap and sprint charts stay empty.
  • Assign release versions to tasks; release health and confidence are grouped by version.
  • Watch Scope Creep % during a sprint, not after it.
You want to… Ask
Create or edit tasks, milestones or sprints An Admin
Change a task’s status or assignee An Admin (or the assigned Developer for status)
Decide QA, developer or admin approvals An Admin
Promote a release to Production An Admin
See an app that’s missing An Admin, to grant app access