# Magesmiths 2nd Story Sprint Planning

divide n conquer TODOs

- [ ] - setup figma board (VG)
- [ ] - spectrum voter component
- [x] - refine scope & intro/overview (SG)
- [ ] - refine schedule (VG)

## Schedule
### 1. Discover (Monday)
#### Intro & Overview
- Discuss, learn, find problems. make sure all big areas are being covered in diverge.
- Most of our time should be spent getting thoughts down into Figma. Uncover core problems that need to be addressed, so that we can expore divergent solutions to those problems.
- Define problem statements.
- Two focus areas.

**A. Product**
*At the end of the sprint, we want to have the following:*
- Output: What are our priorities over the next 6-12 months?
- Pre-mortem: What will make us fail? How can we mitigate?

**B. Magesmith Process**
*At the end of the sprint, we want to have the following:*
- Output: MVP implementations of mitigated, improved processes
- Pre-mortem: What will make us fail? How can we mitigate?

#### Timing
- 15 mins: intro/overview
- 25 mins: Product
- 5 mins prompt
- 5-10 mins braindump
- 10-15 mins discuss
- 50 mins: Process
- 5 mins prompt
- 5-10 mins braindump
- 10 mins discuss
- 5-10 mins braindump
- 10-15 mins discuss

### 2. Diverge (Tuesday)
Async divergent work, individuals explore solutions on their own.

### 3. Converge (Wednesday)
Everyone presents main highlights from their findings, and we get consensus on what we should explore further as prototype implmenetations.

### 4. Prototype (Thursday)
Async, collaborative work, mvp implementations of solutions.

### 5. Test (Friday)
Review implementations together and decide where we should focus for max impact / low effort. Prep findings/recommendations for presentation to warcamp on Monday.

## Scope

#### A. Product - 25 minutes
What are our goals? What's our north star?
- What outcomes do we want to achieve/realize?
- Where/when should we focus on infrastructure vs. new features?
- How should we balance requests from existing and new communities? where on the spectrum?
- Where/when should we seek community contributions vs. executing on our own?
- is there anything magesmiths should buidl to help our internal processes and possibly export for other camps to use to improve theirs?

##### Sprint Outputs ->
- Pre-mortem: What will make us fail? And mitigations
- What are our priorities over the next 6-12 months?

#### B. Magesmith Process - 50 minutes
first prompt to get ideas flowing towards the goal

we need to find a way to maintain and build on our momentum while simultaneously operating in a much broader, more open, and more distributed environment

we are in transition, with community growing along with capabilities, and we should try and smooth out our processes to limit friction and coordination failure. enabling maximal, yet sensible innovation and maintenance of the product as well as its community (magesmiths)

what are core problems of current contribution recognition? differentiate between current and presumed based on more open group.

- how we determine what other skills we need
- how we find and onboard contributors
- how we work
- how we track and recognize contributions
- how to facilitate and accept external contributions
- how do we interface with hausdao and uberhaus? (feedback loop/collaboration)
- how do we keep membranes permeable, not siloed? (freedom of information act)

##### Sprint Outputs ->
- Pre-mortem: What will make us fail? And mitigations
- mvp implementations of mitigated, improved processes