Beginnings of a **Strategy for delivering 5 lessons by end of Season

What is the purpose of this document. Oh no, not yet another document!** We hope to have this as a (living document) list of easy and durable questions that we can use through the life of the project. Why? So we can communicate easily among ourselves as a team on our needs to keep the project moving forward. This in turn will help us efficiently and succinctly communicate with one voice on our direction and needs to the wider DAO and externally.

Authors: education-team Phil. Tito, Qaf, Rohit, Piablo and with-heart

Feedback on this document is welcome. Please add feedback as comments in the side bar

1A. Core questions we always need to ask each other/ourselves before reaching out:

Why do we ask for help? Who/where do we and don't we ask for help? When do we and don't we ask for help? When we know and can clarify the above - How do we ask for help?

B. We start to keep by keeping it simple and modular (we should hopefully be able to answer the following in one sentence):

STG: Short term goals: MVP (Deploy + 2 Lessons)

MTG: Mid term goals: Forum, Pomodoro, 5 Lessons

LTG: Long Term Goals: Have a self-sustainable community within an education platform

ATG: All Time Goals: values, I guess!!!

Questions as of 25 June 2022

how can we ‘measure’ our personal and team well-being? active listening; we can check-in to and check-out of all our meetings ATG how can we help ensure that our personal and team well-being are looked after? active listening and respond mindfully to our check-in/check-outs; we can do retros periodically, explore other methods e.g. Process Work; delegate tasks e.g. communication; agree on how/when to ping each other ATG
what constitutes this as a 'finished product' for end of season 1? → Mid Term Goals what is needed from smart contract lessons point of view? → Write remaining 3 lessons MTG what is needed from fundamentals (drawers) lessons point of view? → Write some more flash-cards STG & Define a term to identify this component STG what is needed from proof reading lessons point of view? → Experienced/Technical DAO members review the lessons ATG / Smart Contract auditing feedback loop into the lessons ATG & Proof reading of fundamentals STG what is needed from front end point of view? → Review PRs and see if we have more issues to solve STG. Figure out styling of lessons, drawer components, how to pass the data to the components STG. what is needed from data storing and hosting point of view? → Choose sustainable path for Data storing and hosting STG what is needed from design point of view? → Define architecture and structure for lessons and drawers STG, and after that, design the lesson pages STG who is our intended audience? → Devs aiming to onboard into web3 with no particular level of skills ATG what assumptions are we making about our audience? → They understand eEnglish. LTG? They need no previous dev background. They are using a computer (not a phone)LTG. They know how to use a terminal n/a. Slightly tech savvy ATG who can we test on? → Currently only DevDAO volunteers MTG at what stages can we test? → MVP Ready (alpha test - innovators, not yet deployed for the public) STG. Twitter audience (beta test - early adopters) LTG gathering/analyse feedback > ATG what approach are we taking to funding? Funding from entities that don't conflict with our core values, and funding doesn't jeopardize our team or the DAO in a legal manner. ATG

and we add to this list what is needed, high level. Then make it more granular, follow this by making a simple timeline, and then we can start identifying people we do and don't need.

This will help us to communicate visually and textually internally and externally.

.