# Sprint & release cycle ideas

Ideas for "bundles" of work we can work off of one by one (as releases or sprints if you will). Main thing is that we get a group of people to focus their time on something specific so it gets done.

---

### Sprint planning call on April 19, 2021

Sprint #4 goals
-

### Sprint planning call on March 29, 2021

Sprint #3 big goals
- Get more content reviewed with community
- Friday best for Daniel, Mon/Wed also good

- Payments section content development
- Transactions (merged)
- Sending (maybe merge based on review)
- Receiving (HackMD -> clean-up and illustrations)
- Transaction privacy (starting from scratch -> draft & PR & Figma layout)
- Onboarding section content development
- Backing up recovery phrase (Figma -> HTML)
- Seedless backup (Figma -> HTML)
- Manual seed phrase backup (Figma -> HTML)
- Creating a wallet (Doc -> Figma)
- Protecting a wallet (Doc -> Figma)
- Funding a wallet (Doc -> Figma)
- Images
- Add missing ones (can be placeholders, [#190](https://github.com/BitcoinDesign/Guide/issues/190))
- Content
- Cross-linking ([#191](https://github.com/BitcoinDesign/Guide/issues/191))
- Proof-reading (grammar, typos)
- Proof-reading (does it make sense)
- Consolidate
- Clean up source files and make them available
- Site optimization
- SEO
- Performance
- Accessibility
- Mobile
- Search functionality
- Theme clean-up

Other issues
- [Recovery backup storage 101](https://github.com/BitcoinDesign/Guide/issues/139) (Doc -> Github)
- [Define audience for the guide](https://github.com/BitcoinDesign/Guide/issues/51)
- Bitcoin icon set project page (and domain?)
- Case studies?
- [Research resources landing page](https://github.com/BitcoinDesign/Guide/issues/111)

---

Notes from planning call on Feb 15.
- How to format recommendations
- Glossary not that exciting
- Page about manual backup techniques - in-progress
- Case study sprint
- Section landing page
- Lift out content into new section
- Design page template
- Onboarding and payments - next goals for sprint #1?
- Ensure we allow others to follow along and participate on things they care about
- Make smaller tasks available ("good first task")
- Ask who is interested (reviewing, helping, etc)

---

### Guide V1 end of Q1

What do we still need to get done for our first major version of the guide we want to publicly post about?

Via [Pavlenex](https://github.com/BitcoinDesign/Guide/discussions/153#discussioncomment-373171):
- Introduction section
- Onboarding section
- Private Key Management
- Payments
- Principles/Foundation
- Clear process on how to get involved (Contribute section)
- Wallet UI Kit
- 1 collaboration

Quality:
- Comprehensive
- Communicates clearly
- Actionable & useful
- Free of mistakes

### 1. Principles section ([Sprint 0](https://github.com/BitcoinDesign/Guide/milestone/1) & [Sprint 1](https://github.com/BitcoinDesign/Guide/milestone/2))
Extract principles from other sections (Private Key Management and upcoming Onboarding and Payments) and create a dedicated section. This avoid repetition and creates more consistency.

Todos:
- Gather principles we have already written about
- Create a doc, clean-up, iterate and review
- Create illustrations
- Implement

### 2. Case studies section

Extract the case studies from the Private Key Management into a separate section. Expand those case studies so they include more best practices and can also be referenced by other content. This avoids repetition and creates more consistency. Should also make it easier to have reference designs as each page author doesn't have to start from scratch.

Probably multiple sprints:
- one sprint to extract prototypes into dedicated pages with enough info to be standalone (done in [Sprint 1](https://github.com/BitcoinDesign/Guide/milestone/2))
- second sprint to revise case study format
- extra sprints on individual case studies
- integrate with the wallet UI kit?

Todos:
- Design a case studies page in Figma first and get consensus on the format and content (done in [Sprint 1](https://github.com/BitcoinDesign/Guide/milestone/2))
- Figure out how to reference case studies from other page once they are extracted
- Implement

### 3. Glossary

Beef up the glossary:
- Ensure it covers all relevant terms
- Ensure covered terms are linked in the rest of the guide
- Revise descriptions and visuals
- [Improve interaction model](https://github.com/BitcoinDesign/Guide/issues/43) (expand/collapse, search)
- Extract long descriptions into sub-pages
- Create sub-pages for [coin selection](https://github.com/BitcoinDesign/Guide/pull/90) and [hiding sensitive info](https://github.com/BitcoinDesign/Guide/pull/112)

**5. Design process section (idea)**
Created a new section that includes information about user research, design tools and workflows and other practical information and tips that help designers and projects to practice design well.

Page ideas:
- User research & testing
- Usability & accessibility
- Product discovery
- Design systems
- Design file collaboration
- Wallet UI kit
- Community project support

Todos:

Team:

---

## Completed

### 4. Contribute section (almost done)

Create a dedicated section that explains how to contribute to the guide.

_Pavlenex working on this_

Todo:
- Section landing page (update as sub-pages get done)
- Target audience ([issue](https://github.com/BitcoinDesign/Guide/issues/51))
- How to propose ([PR](https://github.com/BitcoinDesign/Guide/pull/125))
- Content guidelines (done)
- Illustration guidelines (done)
- Formatting (done)

Team:
- Pavlenex
- Paulo
- Christoph

**Open issues**
See [Github](https://github.com/BitcoinDesign/Guide/issues)

### Project collaboration (done)

Create a playbook for how the community can offer design support for projects. Includes initial project briefs, how to run projects, etc.

Todo:
- Where to store these briefs? Meta repo issues?
- Iterate the [document](https://docs.google.com/document/d/1vHHauCktbITPqKApQ5h-i7cFh4W5Y-qqVcpUvlZKKFY/edit?usp=sharing) as a group
- Add content to meta repo as `project-collaboration-playbook.md`

Team:
- Pavlenex

---

## Other ongoing work

Carried by individual contributors.

**Onboarding section**
Worked on by Maggie and Conor.

**Payments section**
Worked on by Johns.

---

## Sprints?

- A way for regular contributors to organize, prioritize and plan tasks they want to get done.
- On a 3-week cycle, aligned with the community call and the newsletter.
- Organized via Github milestones.
- Does not cover all ongoing work. People can work on whatever they want.