# Burner Collective Sprint Process

To start iterating towards [its purpose](#Burner-Collective-Purpose), and prove that the collective can deliver stable software aligned with [its mission](#Burner-Collective-Mission), it is proposed to divide the general development process in smaller sprints. Sprints should have a limited scope (< x000 DAI), and specific goals (improve modularity or integrate burner-core). Sprints are composed of a set of sized bounties, and marked with a [github milestone](https://github.com/austintgriffith/burner-wallet/milestones).

### Defining Sprint goals and scope

Sprint goals and scope (in DAI) are set by the 3 wings of the burner collective.

### Scoping and sizing a sprint

1. A list of candidate issues is added to the **To Do:** column of the [bounty board](https://github.com/austintgriffith/burner-wallet/projects/1).
2. A [planning poker](http://planningpoker.com) meeting is scheduled with 3 - 6 participants that represent the interests of all wings and have the technical experience to estimate the complexity of development tasks.
3. During the planning poker meeting all issues are estimated with t-shirt [sizes XS(200DAI) to XL(1400 DAI)](https://github.com/austintgriffith/burner-wallet/labels?utf8=%E2%9C%93&q=size). During the meeting, issues by issue, participants are selecting cards and all the cards are turned at the same time. Participants are free to discuss complexity, challenge choices. selecting and turning cards is repeated until all have chosen the same size. Participants should NOT start negotiating numbers or applying time durations to t-shirt sizes.
4. If the sum of the t-shirt sizes exceeds the sprint complexity, the issues are ordered by priority and the least important removed, until the size =< sprint complexity.
5. All issues are labeled with the bounty tag, as well as the respective size label. The issues remain in the **To Do:** column.

### Sprint execution

During the sprint execution any-one can participate by choosing a role on the different issues:

**Gardener (10-30% of bounty size):**
- writes a detailed issue description following the structure of the [bounty template](https://github.com/austintgriffith/burner-wallet/blob/master/.github/ISSUE_TEMPLATE.md)
- approves a worker on the issue and monitors delivery (WIP PR) to prevent stalling
- once an issue is labeled with size and has a gardener, it is moved to **Available:** column
- once a bounty has work submitted (open PR), the gardener helps the worker to find a reviewer
- once a review is completed, and the PR merged, the gardner requests payout from the multisig ([sizes XS(200DAI) to XL(1400 DAI)](https://github.com/austintgriffith/burner-wallet/labels?utf8=%E2%9C%93&q=size) is split according to percentages between gardener, worker and reviewer).

**Worker (40-80% of bounty size):**
- picks a bounty from the **Available:** and asks the gardener to assign him
- once a bounty is assigned a worker, it is moved to the **In Progress:** column
- creates a WIP PR ASAP.
- notifies the gardener ASAP about delays or unexpected complexity
- when ready for review the worker removes the WIP attribute from the PR
- finds a reviewer by moving bounty to **Ready for Review:** column on [bounty board](https://github.com/austintgriffith/burner-wallet/projects/1) and posting in chat.

**Reviewer (10-30% of bounty size):**
- tests the PR code and reviews code quality and syntax
- review should be thorough, but follow optimistic merging practices
- after completed review the PR is merged, and bounty is moved to **Waiting for Payout:** column.

### Bounty Board

Bounties on this board have the following stages:

- **To Do:** The gardener has proposed an issue to become a bounty. The multi-sig has not allocated funding yet.
- **Available:** Funding to this bounty has been allocated, bounty waiting for worker to pick it up.
- **In Progress:** Some-one is working on the bounty, and will create a PR soon.
- **Ready for Review:** The worker has delivered a first PR. A reviewer is needed.
- **Waiting for Payout:** The bounty has been merged into master. The gardener should request payment for the bounty from multi-sig.
- **Done:** The bounty has been delivered and paid out.

An example for an issue processed as bounty can be found here: https://github.com/leapdao/burner-wallet/issues/116

Transition between the different states is also described in this diagram:


## Burner Collective Purpose

to drive forward the development of the Burner Wallet by rewarding those that contribute to pushing forward the mission and collect revenue from engagements, grants, and custom burner app/game builds.

## Burner Collective Mission

**In the short term**, the Burner will drive onboarding by being irresistibly easy to use to move small amounts of crypto within the ecosystem and at events. 

**In the near term**, the Burner will act as a platform for games and apps. 

**In the long run**, the Burner will drive mass adoption, be ubiquitous in the space, and act as a cash replacement.