DGF SCRUM Ceremonies

From DAO Governance Wiki
Revision as of 18:27, 18 April 2023 by Craig Calcaterra (talk | contribs) (Text replacement - "Availability" to "availability")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

2/1-2/8/2023: Blochain Production/Use Case Sprint[edit | edit source]

News:

Review:[edit | edit source]

  • Attendance: Jonathan Kung, Ladd Hoffman, Craig Calcaterra
  • Work Accomplished:
    • Calcaterra: Mauritius students and personnel have poor blockchain foundations. Close to finishing reputation tokenomics paper.
    • Hoffman: Fleshed out some ideas for next steps: block production, exchange, storage
    • Kung: DeSci Denver organizing and presentation preparation.
  • Discussions:
    • Multi-DAO reputation interfaces. Muti-reputation DAO infrastructure.
    • Next Steps:
      • Storage
      • Exchange
      • Block Production

Planning:[edit | edit source]

  • Action Items: Reputation tokenomics Sprint Continues
    • Calcaterra: Work on paper.
    • Hoffman: Work on block production and use-case scenarios.
    • Kung:
      • Have the ceremonies tied to the roadmap that Kung will be building out.
      • Send out Executive Summary for National I-Corps
      • Write out roadmap for sharing
      • Apply to incubator programs
      • Hash out some database details with Weavechain/OpSci

Retrospective:[edit | edit source]

  • What did we do right in the previous sprint?
    1. Reviewing otter.ai transcripts.
  • What did we do wrong in the previous sprint?
  • What should we start doing in the next sprint?
    1. Have the ceremonies tied to the roadmap that Kung will be building out.
    2. Determine metrics and a better template for SCRUM Retrospective.
    3. Kung needs to go through the SCRUM class.
  • What should we stop doing in the next sprint?
  • What can we do to improve productivity?
    1. Hiring. This not been addressed.

1/25-2/1/2023: Reputation tokenomics/Consensus Protocol Sprint[edit | edit source]

News:

Review:[edit | edit source]

  • Attendance: Jonathan Kung, Ladd Hoffman, Craig Calcaterra
  • Work Accomplished:
    • Calcaterra: Mauritius students and personnel have poor blockchain foundations. Close to finishing reputation tokenomics paper.
    • Hoffman: Fleshed out some ideas for next steps: block production, exchange, storage
    • Kung: DeSci Denver organizing and presentation preparation.
  • Discussions:
    • Multi-DAO reputation interfaces. Muti-reputation DAO infrastructure.
    • Next Steps:
      • Storage
      • Exchange
      • Block Production

Planning:[edit | edit source]

  • Action Items: Reputation tokenomics Sprint Continues
    • Calcaterra: Work on paper.
    • Hoffman: Working out next directions between storage, exchange, and block production.
    • Kung:
      • Have the ceremonies tied to the roadmap that Kung will be building out.
      • Send out Executive Summary for National I-Corps
      • Write out roadmap for sharing
      • Apply to incubator programs
      • Hash out some database details with Weavechain/OpSci

Retrospective:[edit | edit source]

  • What did we do right in the previous sprint?
    1. Reviewing otter.ai transcripts.
  • What did we do wrong in the previous sprint?
  • What should we start doing in the next sprint?
    1. Have the ceremonies tied to the roadmap that Kung will be building out.
    2. Determine metrics and a better template for SCRUM Retrospective.
    3. Kung needs to go through the SCRUM class.
  • What should we stop doing in the next sprint?
  • What can we do to improve productivity?
    1. Hiring

1/25-2/1/2023: Reputation tokenomics/Consensus Protocol Sprint[edit | edit source]

News: Ladd finished the first pass of DGF buildout.

Review:[edit | edit source]

  • Attendance: Jonathan Kung, Ladd Hoffman
  • Work Accomplished:
    • Calcaterra: Getting settled in Mauritius and started conversations with Dr. Anuja Meetoo and Dr. Kevin Sungkur.
    • Hoffman: Finished first pass of DGF buildout.
    • Kung:
      1. DeSci Denver organizing and presentation preparation
      2. Put together a lightweight roadmap: consensus protocols, storage, search, UI, DxD management, hiring, further funding
  • Discussions:

Planning:[edit | edit source]

  • Action Items: Reputation tokenomics Sprint Continues
    • Calcaterra:
      • Same as last time:
        • Will field out how Dr. Anuja Meetoo and Dr. Kevin Sungkur want to do and whether or not they'd be interested in the various parts of the project.
    • Hoffman:
      • Reputation Lifetimes. Active vs. Passive.
    • Kung:
      • Have the ceremonies tied to the roadmap that Kung will be building out.
      • Send out Executive Summary for National I-Corps
      • Write out roadmap for sharing
      • Apply to incubator programs
      • Hash out some database details with Weavechain/OpSci

Retrospective:[edit | edit source]

  • What did we do right in the previous sprint?
    1. Recordings for review with otter.ai.
  • What did we do wrong in the previous sprint?
    1. Too many meetings were skipped.
  • What should we start doing in the next sprint?
    1. Have the ceremonies tied to the roadmap that Kung will be building out.
    2. Determine metrics and a better template for SCRUM Retrospective.
  • What should we stop doing in the next sprint?
    1. Too early to tell.
  • What can we do to improve productivity?
    1. Hiring

1/18-25/2023: Reputation tokenomics/Consensus Protocol Sprint[edit | edit source]

News: SPD is lightweight sponsoring and organizing DeSci Denver and speaking at DAO Denver and Schelling Point. This event is focused on on-boarding scientists and talented developer while fielding concerns and skepticism about the boom. These events are happening around ETH Denver so we can seduce talented developers from the DeFi space.

Review:[edit | edit source]

  • Attendance: Jonathan Kung, Craig Calcaterra
  • Work Accomplished:
    • Calcaterra: Getting settled in Mauritius and started conversations with Dr. Anuja Meetoo and Dr. Kevin Sungkur.
    • Hoffman: Created a plan for adopting Ethereums consensus layer to DGF's Proof-of-Reputation.
    • Kung:
      1. DeSci Denver organizing
      2. Worked on SPD UI: Congested mix of CRDAO, Wikipedia, Web of Science
      3. Otter.ai setup for 1xperson (Kung) at the moment (specifically for weekly calls and interviews).
      4. Put together a lightweight roadmap: consensus protocols, storage, search, UI, DxD management, hiring, further funding
  • Discussions:
    • Mauritius: Calcaterra is interested in building out the the chit fund and insurance/underwriting applications of DGF and hope to rope Dr. Anuja Meetoo and Dr. Kevin Sungkur in.
    • Consensus Protocols: Landscape and plan of attack?
      • Craig knows the math. Though no one is an authority, his recommendation is that Hoffman studies Ethereum's documentation and executes the plan to rework the Ethereum's consensus layer.
    • Storage: Weavechain and OpSci collaboration for MVP.
    • DxD: Maciej for execution? Politics.
    • Hiring: Maciej? Mauritius contacts? Need to probe network more for thoughtful blockchain, AI developers.

Planning:[edit | edit source]

  • Action Items: Reputation tokenomics Sprint Continues
    • Calcaterra:
      • Will field out how Dr. Anuja Meetoo and Dr. Kevin Sungkur want to do and whether or not they'd be interested in the various parts of the project.
    • Hoffman:
      • Read through Ethereum consensus protocol documentation and continue with adapting Ethereums consensus layer to DGF.
      • Tune up availability and Business smart contracts.
    • Kung:
      • Have the ceremonies tied to the roadmap that Kung will be building out.
      • Write out roadmap for sharing
      • NSF National I-Corps Industry Mentor decision
      • Apply to incubator programs
      • Hash out some database details with Weavechain/OpSci
      • DGF UI

Retrospective:[edit | edit source]

  • What did we do right in the previous sprint?
    1. We cut down standups to 10-15min.
  • What did we do wrong in the previous sprint?
    1. Too many standups were skipped. Some reasons were legitimate, others were not.
  • What should we start doing in the next sprint?
    1. Have the ceremonies tied to the roadmap that Kung will be building out.
    2. Determine metrics and a better template for SCRUM Retrospective.
  • What should we stop doing in the next sprint?
    1. Too early to tell.
  • What can we do to improve productivity?
    1. Otter.ai was setup.

1/11-18/2023: Reputation tokenomics Sprint[edit | edit source]

Review:[edit | edit source]

News: Craig is traveling to Mauritius 1/21. We will see if his colleagues there will be interested in what we are doing.

Review:

  • Attendance: Jonathan Kung, Craig Calcaterra, Ladd Hoffman
  • Work Accomplished:
    • Ladd worked Forum "refund" code. Also refit ERC721 base code to fit DGF. Each post is now an NFT with the property value changing rather than how Craig had originally conceived of an "in-system" fungible NFT. Ladd's solution is more elegant.
    • Kung is finishing up NSF National I-Corps application via documentation around kickstarting a DeSci/MetaSci Consortium with 100x published interviews.
  • Discussions:
    Ladd has been working on "Node Spec." "Storage Spec" comes next.
    Ladd's code, how to apply it to a consensus protocol, and next steps (passive and active reputation). Figure shows where we are according to Ladd SPD-3 drawing

Planning:[edit | edit source]

  • Action Items: Reputation tokenomics Sprint Continues
    • Hoffman:
      • Work on 1xreputation consensus protocol implementation.
    • Kung:
      • Setup meeting transcription for meetings
      • Setup Roadmap

Retrospective:[edit | edit source]

  1. What did we do right in the previous sprint?
    1. Start sprinting.
  2. What did we do wrong in the previous sprint?
    1. Too early to tell. Daily standups have been taking 20min for 2x people. We should try to cut it down to 10-15min.
  3. What should we start doing in the next sprint?
    1. Have the ceremonies tied to the roadmap that Kung will be building out.
  4. What should we stop doing in the next sprint?
    1. Too early to tell.
  5. What can we do to improve productivity?
    1. Otter AI setup to record and summarize review and planning meetings.