You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

7/1

Meeting to discuss powerpoint for presentation tomorrow. 

End goal: get everyone on call to add name to wiki page and talent.

Send off with thought how Giving Chain can work this time 


Cover:

What happened ( 2019 Giving Chain)

Where We are now ( starting with new goals and resources)

Forecast

6/28

Discuss meeting: suggested time from survey is 12 noon fridays. To Do: Bobbi sent a rocket chat message to Ry Jones to set this meeting up.

Survey : 2 developer have an interest

Presentation: Hardik will get a presentation together and we will review Wednesday  Bobbi to set meeting.

Website - set up so other have edit access.

Donations - start discussion on funding, how much support from hyperledger?  

QUESTION: DO WE HAVE A GITHUB REPO? 


HAVE ALL FOLK ENDORSE ON SOCIAL MEDIA !!!

6/23

Check to make sure test form was received. Send welcome email and survey. Blast survey to events and social media accounts

Web site ideas _ basic format and information

Set Up Framework for project work.

Weekly checkpoints

Weekly checkpoints are meant to guide you to think through your own solution prototype, stay on track, and ultimately formulate your own Blockchain  / White Paper / Projects. 

Each week is designed to address a particular set of questions. 

Week 1: Impact Opportunity

    • Define Project and team members.
    •  Select your challenge requirements.
    •  Define the scope of problem you are addressing.
    •  Why is blockchain needed to solve this problem?
    •  What is the size of the market? What demographics will you serve? Which industries will you impact? Any concurrent trends?
    •  What are some current solutions to the problem you identified? Do they work effectively?
    •  Who are the stakeholders involved? How are they thinking/feeling/acting currently?
    •  What are the geopolitical, cultural-social-economic factors that must be taken into consideration? What are some nuances and complexities that must be addressed?

End of Week Presentation 


Week 2: Business Model Validation

  •  Who are your clients/users? Sketch out the persona of your user.
  •  What are their pain points? How does your solution solve them? Indicate your unique value proposition.
  •  Does your solution depend on context? Can it be scaled?
  •  What is your go-to-market strategy? Who can you partner with?
  •  How will your product generate revenue / benefit ? Will it be financially sustainable in the long-term?
  •  What are the implicit and explicit assumptions being made in your business and financial model (user-profiles, partnerships, costs, etc.)? How do you plan on validating them?
  •  What is the vision for your product? Can it significantly change the current state?

End of Week Presentation


Week 3: Technical Architecture

  •  Define the technical specifications of your system's architecture. Include a description of system requirements, processes, business logic, technology stack, user flows, attack factors and any other technical specifications. Attach some visuals as bonus.
  •  Define your Minimum Viable Product (MVP) testing approach.
    •  Marketing Tests: Landing Page, Explainer Video, Ad Campaign, A/B Tests, Crowdfunding
    •  Product Tests: Sketches, Wireframes, Mockups, Interactive, Prototype, Wizard of Oz, Concierge, Live Product
  •  Outline a development roadmap with a realistic timeline that takes into account your product vision, market readiness, team capabilities, functional upgrades and testing plans. What are your goals for each phase? How will your product evolve? Will you integrate other technologies?

End of Week Presentation 


Week 4: Impact Measurement

  •  What is the impact goal of your solution? How do you ensure to capture needs of those who are traditionally underserved within your category?
  •  What are the key indicators that capture your impact goal? Are they compatible with globally recognized standards (e.g. IRIS, SROI, PPI)? Do you have impact measures to add to create a more equal and inclusive solution?
  •  What variables and data points do you need to collect? What are the tools and processes to collect those data? What are some obstacles you may face on the ground? Infrastructure issues, measurement techniquest, etc.
  •  How do you collect feedback? How do you improve your measurement?

End of Week Presentation


Week 5: Code

  •  Prototype your solution in some manner. Examples include:
    •  Working code
    •  Analog prototype / Mock-ups
    •  Tech Stack and Wireframes
    • Create blockchain and implement.

End of Week Presentation


Week 6: Final Submissions Due


  •  Integrate  information  into a White Paper, , White Paper is your chance to incorporate new information after your submissions of weekly checkpoints.
  •  Prepare a 5-min video demo that includes the following:
    •  A description of your early stage idea: The challenge of your choice and the overview of your solution.
    •  An explanation of your business model: How does your solution create value and be financially sustainable?
    •  Prototype / Proof-of-concept: A minimum viable product that captures how your product functions.
    •  Timeline for sustained development: A plan for project's growth beyond the scope of the incubator.
    •  Bonus: Include how you addressed increasing Diversity and Inclusion. How did this goal impact your team, the product, the research methods, the target groups and any other way you came up with. (To qualify for The One World Award you also need to submit a 2 pager. see above)


 

6/21

Link for : https://medius.studios.ms/Embed/video-nc/d7dc4c4d-b7fa-450a-b1ad-307060975865?r=857072506436


Hardik: Finish up survey and send out to list, and Hyperledger Chat rooms (LMDWG, Meetup and General) - https://forms.gle/SpBZCPaLAFjsFcGZ7


Re-do survey for a quick social media campaign (Linkedin  telegram and Twitter) 


Web Site : Have copy of Survey for folks who just find us through the site.

  Re visit design of www.thegivingchain.org
New theme and graphics, and content. 
 



6/16

https://nonprofits.tsi.microsoft.com/Thank-You-Volunteer-Management-Public-Preview-Application-Form/?recipientid=3a959001-bece-eb11-ba5e-00155dd3b166

Joined for preview

6/14

Next steps:

Discussion during LMDWG call:

  • Complete Survey, gather more emails, and contact Jim S . for his comment for Welcome letter 
  • Set up Mentorship Check in calls 1pm edt every other Monday (begin 6/21)

Response

Bobbi

Added emails from older project for welcome letter and survey.  Do you think we should send just the survey with a short blurb about the project ( maybe link to website if ready) to meetup groups and linkedin connections to see in there is an interest from folks outside Hyperledger in joining?

Emailed Jim for information for Welcome letter

Reviewed Survey:  looks great, Do you think we should ask where they see themselves contributing to get folk hooked into  project or is it too soon?

Hardik 

https://forms.gle/HvxtPzrvvnBp19iF7 Take a look, What else should I add? Or are there are any specific changes that you may like. .

6/7 Email Thread

Hardik,  I have  a few suggestions on your recent email.



  • I'm planning on creating a page under https://wiki.hyperledger.org/display/LMDWG/Mentorship+Programs where I will keep all the notes and the achievements that we have made towards the goals. 
  • For the mailing list, I will ask around my friend circle to see if I can get a few people to join us. Also, shall I ask other mentees too? What do you think?
  • I totally under the importance of the invitation email, I will try my level best to create a compelling email body. Will be ready by our next project call!
      • I have started the welcome email and put my work on the letter on the wiki, Jim and Hardik please edit and fill in what you want to say to potential members to inspire them to get involved. We can go over it at the next LMDWG call and then send it to everyone on our email list. 
  • For the form, I have a suggestion. I think that giving choices for the meeting time would be much better than asking the group for their best time. It will create less confusion. For example 
      • Hardik that is exactly the way we need to whittle down to get the most convenient time for everyone. I started a Google Doc for us to edit. Jim,   please edit for information you think will be relevant to have from potential team members. 
        https://docs.google.com/forms/d/1J1DBvB-oXhugVDflI3QC77ggDhqFn2pLbOXQHy2CCvg/edit
        and Hardik please work on the overall form and relevant information you would want from the team.  We will review at the next LMDWG call.
  • I can also make it such that we will be asking for their best time. So which one do you prefer? Also what more points do you think we should include. Name, time zone, best meeting time, meeting preference weekly or bi-weekly are what I can think now.   
      • The more idea we have the better, ask more questions. 

Jim, so glad we will be working together on help Hardik and team get the Giving Chain operational, please email questions and put edits on the wiki. Talk soon,
 
Bobbi
  • No labels