web3/meta/projects/roadmap-v0.1.md

111 lines
5.0 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
created: 2022-03-10
---
# Get a Roadmap v0.1
What & Why: We want a clear near-term roadmap with associated tasks so that
* we know what to prioritize
* have goals (to inspire us)
* can efficiently self-organize in a distributed, part-time and part-volunteer team
## Acceptance
A clear near-term (1m) roadmap and a vaguer 6m roadmap in [plan](../plan.md)
* [ ] Milestones / Goals
* [ ] Rough timeline
* [ ] Next actions
Meta (how we organize)
* [ ] Team structure
* [x] Scrum Lead **✅ Eilidh**
* [x] Product Owner **✅ Rufus***
* [ ] Team process
* [ ] Clear PM infrastructure (e.g. are we using markdown/hackmd/git/obsidian or gdocs)
* [ ] Can we do all the work "in the open"?
* [ ] Materials
* [x] Existing materials are tidied up (e.g. PA10) **✅ 2022-03-11 DONE except for job stories**
## Tasks
* [x] Prep
* [x] Background reading
* [ ] Backlog generation
* [ ] Prioritization
* [ ] Summary
* [ ] Misc
* [x] Consolidate our claims database stuff in one place ✅ **2022-03-11 have consolidated on coggle for now**
### Prep
General concepts of project management
* [x] Read about agile delivery playbook.datopian.com/agile/ **✅ Read it and clarified questions**
* [x] Read about PARA https://www.lucapallotta.com/para/ ✅ **Read**
### Background
* [x] Read the PA10
* [x] Read it all the way through quickly **✅ Read it**
* [x] Note questions (in the doc using comment facility) **✅ Read it**
* [x] Add TODOs for key info in the doc (maybe list here). Suggest answers and then check with Rufus ✅ **Added TODOs as comments**
* [x] Material to process (or process out)
* [x] Plan of Work brainstorm ✅ **Processed and deleted**
* [ ] Job Stories
* [x] Key claims list ✅ **Processed to coggle claims taxonomy and deleted**
* [x] Key aspirations ✅ **Processed to coggle and deleted**
* [ ] Read meta folder https://github.com/life-itself/web3/tree/main/meta
* [ ] plan
* [ ] design
* [ ] Read issue tree https://docs.google.com/spreadsheets/d/12Yh1kuxH4uoposLUJsJifM2W_zixkAhlc7QgcKavfls/edit#gid=2049708942
## Brainstorm and Organize Plan
🚩 already have issue tree and plan.md - do we need to do more and if so where ...
### Simplification of tools and process for content
H: Consolidate and simplify material and structure
Why?
* S+C: using 3+ locations atm and several tools
* we have google docs (docs & sheets), git, coggle, excalidraw etc
* Markdown in github (with obsidian)
* coggle
* even core team members a bit confused over all the locations of stuff
* Want to get clear on what we use for what.
* H: consolidate on the wiki using coggle only to provide overviews or brainstorm.
* What about meeting notes etc?
Concrete example: aspirations and claims "database" => see the next item.
### Consolidate our claims database stuff in one place
Currently have 4 locations for claims. We want to consolidate on one.
* [x] Consolidate overview of the aspirations/claims
* [x] What are current locations? ✅ **2022-03-10 currently 4 locations: In Issue Tree spreadsheet a) "Claims" b) "Aspirations and Claims"; then also c) https://coggle.it/diagram/YhTzF8ZnKihmLdpm/t/web3-taxonomy-of-aspirations-and-claims d) claims list in wiki https://github.com/life-itself/web3/tree/main/claims here**
* [x] Choose location for overall list ✅ **Consolidate on coggle https://coggle.it/diagram/YhTzF8ZnKihmLdpm/t/web3-taxonomy-of-aspirations-and-claims (for now as of 2022-03-10) as the best version. Next would be to converge with wiki**
* [x] Move brainstorm of aspirations/claims from gdocs to the coggle ✅ **there was only fairer and stable economy section and most already there so not much to move. Have deleted from gdocs**
* [x] Move from apirations & claims spreadsheet **✅ All already there**
* [ ] Consolidate wiki list https://github.com/life-itself/web3/tree/main/claims to coggle
* [ ]
* [x] Consolidate on a page on the wiki as focal location
* [x] Create the index page
* [x] Where? `/claims/`
* [x] Do we embed the coggle? ✅ Yes, at least to start with
* [x] Do we list on index page the other claim pages in the wiki (and how)? ✅ **For now we won't. In future we can use our CMS system to do so.**
### Misc
* [ ] 🔽2⃣ Process job stories brainstorm somewhere https://docs.google.com/document/d/1AV2xXDgTiNRVv6_M7CoGhiFl8pBj5hDGi_qdsHOU_3M/edit#heading=h.g248tv329855
* [ ] Where? ✅ **`meta/job-stories` in the wiki and just remove any identifying info from user interviews**
* [ ] Why? ✅ **Job stories help us prioritize our efforts (plus motivation for ourselves and others as to why we are doing this). E.g. if we know what journalists are looking for X we can focus on that which seems a high impact thing to do.**
* [ ] What are questions / topics we should write about?
* A useful tool which collects google searches people are making about web3: https://answerthepublic.com/reports/54ce111d-ff4f-49fa-b2de-411695bd9910 These would make useful titles or section headings in blog posts about Web3.
* ![](https://i.imgur.com/tCS26FA.png)