gitcoinbot
commented
5 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 3.626 ETH (500.06 USD @ $137.91/ETH) attached to it as part of the MyBit AG fund.
- If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin Slack
- $42,857.23 more funded OSS Work available on the Gitcoin Issue Explorer
Introduction
At MyBit we are focused on the decentralisation of wealth, which we had been working on through our many applications. By the end of the year, we plan on decentralising the company itself, which means also opening the knowledge that we use for developing our apps.
One of the core ways we are planning to achieve so is by creating a standard baseline for the documentation required for developing applications on top of the MyBit ecosystem. We believe that solid kick-off documentation takes a product long ways within an agile lifecycle, and helps developers have a product scope and goals in check.
The goal of this task is to create a new brand PRD template that we can use across our applications taking in consideration the current DApp ecosystem, thus considering, for example, non-functional features like a proper user experience with Metamask. The document is meant to target web applications that perform interactions with Ethereum contracts and provide a baseline for Product Owners to describe the functionality, scope, and other expectations about the application to be developed.
Requirements
Team member definition. Create a section that describes who will be the Product Owner and a Product Manager of the project, as well as a small introduction on what they are supposed to do. The Product Owner (PO) is the person focused in defining the product vision, scope, and general focus of the product, whereas the Product Manager (PM) is the person focused in ensuring the product success, delivery, and milestones of the product defined by its PO. Alongside, define who other individuals are involved in the project and a section for them to add contact information, role and core skills.
User Stories and Technical Requirements (Functional and Non-functional). Create a section that allows PO/PMs to define all user stories required and expected from the product/application to work. You can base yourself in the general IEEE SRS guidelines for inspiration on what to cover, yet make sure to keep the section lean.
Design Brief. Create a section within the PRD that includes insertion of Wireframes, Styleguides (Brand, Color, Typography) and High-End Mocks describing the look and feel of the product.
Roadmap Add a section in PRD for adding a general Roadmap the product. The Roadmap is defined by a PO and PM, and is supported by everyone involved in the making of the PRD. The Roadmap includes a set of Tasks or Milestones expected to be delivered every week, so it should be in the forms of deliverables, and not dates.
The document needs to be extensive but not exhausting. It should work as a brief that you as a developer would like to receive in order to know how to develop an app that is requested from you. If you don't know whether a section should be included, chances are that it should, so please ensure you go back and forward with the team to get a decision.
To Submit
Additional information
Here are a couple guides on inspirations for creating a PRD https://www.uxpin.com/studio/blog/write-good-product-requirements-document/ https://www.aha.io/roadmapping/guide/requirements-management/what-is-a-good-product-requirements-document-template https://confluence.atlassian.com/confcloud/product-requirements-blueprint-937893675.html
If you have any questions, please don't hesitate to comment on the task. For faster interaction, you can reach the team at our Gitter channel.
Disclaimer
All work completed via the MyBit Decentralised Development Fund is property of the MyBit Foundation (CHE-177.186.963) and may be used, re-used, and/or distributed, re-distributed by the MyBit Foundation for financial gain. The contributor holds no warrant nor claims for any future payments resulting from monetisation schemes originating from the MyBit Foundation or any of its affiliates. Where law permits outside of open source regulations, the contributor is not permitted to distribute any work completed via the MyBit Decentralised Development Fund (DDF) for personal gain.