Goal

By the end of this process, you are able to...

Use the Product Management OS to:

Task Checklist

The steps required to achieve this goal are...

Set up a release

The purpose of a release is to bundle a set of Feature or Bug/Issue fixes to improve the product. Releases should run 1-2 months.

  1. Name the release version in the table

    1. 1.x.x. - Significant, platform-wide change. E.g. Upgrading from Sharetribe to custom platform as the SaaS OS
    2. x.1.x - Set of features that enables an entirely new or significantly new user flow. E.g. user sign in to personal accounts.
    3. x.x.1 - Set of light features and bug/issue fixes that improve a previous release.

  2. Decide which features or bug/issue fixes to include in the release.

    1. Add to a release
      1. Review the "Release Setup" filter. This filter includes all features currently in the backlog.
      2. Select features to include by tagging them in the respective release column.
        1. “Intake” → Feature description has been completed, detailing what it should do.
        2. “Scoped” → Product Manager has assigned Priority and Developer has assigned Effort.
          1. The feature should then be tagged to an upcoming release.
    2. Add to a release
      1. Review the "Release Setup" filter. Status columns definition:
        • "No Status" - Intake. Requests identified in testing or from user feedback.
        • "Known" - Reviewed. Product Manager has assigned Priority and Developer has assigned Effort.
        • "Assigned" - Included. Requests that have been included in a release.

  3. Review with Developer to confirm feasibility of effort required to ship release, including all Features & Fixes in estimated timeframe.

  4. Toggle to the “Release Gantt Chart” in the table to sequence out future releases over time. This is key to ensuring you stay focused on only the highest priority at any given time.

Manage Release Progress

  1. Set up bi-weekly or weekly status checks with the Developer to manage progress.