Retro: April 1, 2022 - HausDAO/daohaus-monorepo-deprecated GitHub Wiki

Miro Board

What is working well?

Vision and Planning

  • larger vision starting to solidify
  • Shared values and approach toward common goals
  • Planning is deep, deliberate, and focused
  • diving projects into bite size pieces
  • Organizing work, knowing what needs to get ready next (from design)
  • Getting specs standardized
  • Having a PM team has helped with alignment and process development. Kept all the weight off a single person
  • Offloading of admin or managerial type tasks from dev to manager is very helpful.
  • I'm wasting less time on developing things that aren't needed

Process and Tools

  • Initial process setup feels well thought out. Is a good start.
    • kanban
    • wiki
  • GithHub Kanban Process is simple and easy to use.
  • We can track work an navigate all the work easier via github
  • The board makes it very clear what everyone is working on
  • divide and conquer
  • I generally know who to talk to
  • The Friday show and tells have been good to get a sense of what people are building and allow us to celebrate individual and team wins
  • Alignment via the Board has been great
  • Future-proofing with  feedback/improvement sessions

Rage

  • Rage Report Process working better than expected
  • Raging has allowed us to learn be better informed for saging
  • rage process and output has been really valuable

Code

  • contract is feeling much more battle tested
  • we have a subgraph mapping all contract events that'll support much of the alpha needs

What needs improvement?

Vision and Planning

  • Opportunity to make tickets/task even better
    • will be working on better templates
    • can refine these with feedback as we continue working thoguh dev on them
  • Planning tickets for multiple dev cycles could be helpful for long term planning_
  • High-level discussion still needs to find space (product-level design)
  • For chunk of work, making sure the goal is clearly understood

Process and Tools

  • More design/dev integration
  • Improve pass off design <> dev
  • Still unsure of what the review process is.
  • Review is taking a decent amount of time.
  • Defining our stages (ie Review -> Done)

Focus

  • Can be challenging to maintain momentum. (likely caused by some of my own distractions)
  • Been a little difficult keeping dev's busy at this early stage
    • I hope mostly due to the early stage
    • worried about more onboarding until we have better defined work
  • Roadblocks are changing pretty rapidly.
  • Making sure folks have time to work
  • Ensuring folks are working on what they want to work on
  • Lots of meetings now as we scale into processes
  • async comms a little mixed up in discord with v2/v3

Rage

  • I guess the main thing is transitioning to sage. How does that process start and when do we start it. Also, the rules of a sage I guess are still WIP.

Growth

  • getting new devs involved
  • integration partners
  • build more hype

Research

  • presenting to outsiders for feedback

What would we like to change?

Design/Development Integration

Review Process