Storj Open Development -Part 2

As you take a look at the road map you will find the description of each issue will contain some of the following:

• Summary

• Pain points

• Intended outcome

• How will it work

• ​​Success metrics

• Links:

  • Product requirements document, example

  • Blueprint, example

  • Test plan, example

  • Figma mockups & prototypes, example

Each issue will have a number of different attributes as well:

• Repository: The Github repository that the issue lives in.

  • https://github.com/storj/storj/issues

  • https://github.com/storj/gateway-mt/issues

• Status: Indicates the progress of an issue

  • Not started - Issue is waiting to be started on

  • On track - Issue is being actively worked on

  • Low risk - Issue is at low risk of not being completed by the estimated completion quarter

  • High risk - Issue is at high risk of not being completed by the estimated completion quarter

  • Completed - We have finished the issue and it's been deployed into production

• Labels: Indicates what areas of the network will be affected

  • Uplink

  • Satellite

  • Gateway MT

  • Node

  • Link sharing

• Team: Indicates which of the Storj Labs engineering teams will be working on the issue

• Objective: Indicates which of the Storj Labs internal 2022 objectives the issue aligns with

  • Be enterprise grade

  • Delight current customers

  • Build for future

• Estimated completion quarter: Indicates which quarter we believe the issue will be completed and deployed in.

• Estimated completion sprint: Indicates which sprint we believe the issue will be completed and deployed in. Issues that have not been started yet or are further than a quarter out, may not have this granular info added.

• Original OKR name: A field we use internally to track how road map issues compare to our original planning sessions and ideas.

• OKR target quarter: A field we use internally to track what quarter we thought we could accomplish the issue vs when it was actually delivered.