jeffemmett
/
web3
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
web3/meta/projects/roadmap-v0.1.md

6.8 KiB
Raw Blame History

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

  • Backlog
  • Prioritization
    • Milestones / Goals
    • Rough timeline
  • Next actions

Meta (how we organize)

  • Team structure
    • Scrum Lead ✅ Eilidh
    • Product Owner ✅ Rufus
  • Team process
    • Clear PM infrastructure e.g. where are we ...
      • Recording meeting notes ✅ ?? GDocs?
      • Recording actions and tasks. Options are: github issues, planning docs in wiki, gdocs, spreadsheet (e.g. issue tree)? ✅ Github issues for day to day tasks. May do larger "epic/project" planning in meta section of wiki. Finally, Issue tree spreadsheet provides overview and we will attach tasks to items there
    • Can we do all the work "in the open"? Pretty much. For some job stories or interviews may need to record privately and process before sharing
    • Are we doing iterations and of what form? ✅ Yes, we are going to do 2 week iterations.
  • Materials
    • Where is the primary location for materials etc e.g. are we using markdown/hackmd/git/obsidian or gdocs? ✅ consolidate on the wiki (markdown + github) using coggle only to provide overviews or brainstorm. More discussion below. For drafting people can use whatever they are comfortable with
    • Existing materials are tidied up (e.g. PA10) ✅ 2022-03-11 DONE except for job stories

Tasks

  • Prep
  • Background reading
  • Backlog and prioritization
  • Summary
  • Misc
    • Consolidate our claims database stuff in one place ✅ 2022-03-11 have consolidated on coggle for now

Prep

General concepts of project management

Background

  • Read the PA10
    • Read it all the way through quickly ✅ Read it
    • Note questions (in the doc using comment facility) ✅ Read it
    • Add TODOs for key info in the doc (maybe list here). Suggest answers and then check with Rufus ✅ Added TODOs as comments
    • Material to process (or process out)
      • Plan of Work brainstorm ✅ Processed and deleted
      • Job Stories
      • Key claims list ✅ Processed to coggle claims taxonomy and deleted
      • Key aspirations ✅ Processed to coggle and deleted
  • Read meta folder https://github.com/life-itself/web3/tree/main/meta ✅ Read it
    • plan ✅ Read it
    • design ✅ Read it
  • Read issue tree https://docs.google.com/spreadsheets/d/12Yh1kuxH4uoposLUJsJifM2W_zixkAhlc7QgcKavfls/edit#gid=2049708942 ✅ have read through issue tree, next action is to add in answers
  • fill in issue tree answers

Brainstorm and Organize 👈

🚩 already have issue tree and plan.md - do we need to do more and if so where ...

Brainstorming major next steps

Re the claims

Outcome vision

  • A page for each major claim in the taxonomy
    • The evaluation progress of each claim
    • The evaluation (e.g. true/false)
    • Aspirations it links to
    • Who's making it and where (big egs)

Random

  • A page for the major episodes we've done as the landing page for them separate from the youtube
    • Where do these go? ✅ /notes/
    • Do we flag them into news somehow? 🚧 someday

Simplification of tools and process for content

H: Consolidate and simplify material and structure => consolidate on the wiki using coggle only to provide overviews or brainstorm.

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.

Misc