--- title: Magesmiths Roadmap Session 06-12 tags: --- # Magesmiths Roadmap Session 06-12 Original forum post: https://forum.daohaus.club/t/roadmap-proposal-team-rage-team-sage/9839/4?u=jord **Benefits of Rage/Sage** - Sage team can reskin & rebuild V2 into DAOhaus V3, while the Rage team can experiment with use cases & understand how Baal works. - When our infrastructure is ready, we can get different modular teams to work on problem statements or experiments (i.e. "Open Rage") - We start with 80% here, so that we can enable Rage in the long run - Meme: We care about creating a good core product, but also testing out and experimenting on the edges. This helps you (as a user) have a product that's safe to use & constantly trying to do things better. When splitting into 2 teams, is it just how code is pushed or a split in organisational process? - Standups and meetings are still held together. Team Sage is a smaller team who experiments, while the majority of the team are on Team Sage - Can a single person contribute to both teams? There are key players that contribute solely & deeply on each side (e.g. project management), but some will go in-between. If I'm a Sage and occasionally I want to go on Rage Mode, how can I enable that flexibility, while keeping to timelines? - Could the Team Rage & Sage swap roles periodically? It might lower efficiency on both sides, but it reduces silos, help us do our respective work better, build empathy & teamwork. - What is the optimal cadence? 3 week, 1 week? - When do we want to start this flexibility? ## Milestones & Deliverables (over 2 months) `To be Prioritised` ### Team Rage **Magesmiths** - Create a polished Yeeter product - Create a Baal experiment for ETH Denver, so that participants can have something to play with - Improve the Boosts architecture and clean up current repositories, so that Boost devs can start building Boosts **Rangers** - Create Experiment format, store Experiments somewhere and write about these Experiments > * New product scoping, requirements & education can be shipped via Team Rage, so the product looks like it is moving > * Eventually, this might become like Raids in Raid Guild. ### Team Sage - Re-build V2 functionality in a modular way (estimated to take 4-5 months) - Maintain V2 product, fix bugs and minor improvements to a quality experience - After delivering V2, we then make a decision on whether we want to: - Add Baal to the new V2 - Extract DAOtools - Open items: - Integrate Memes & HAUS token into the product ## Next Steps - Amos/Ven/Jord: **Create roadmap with workstreams** for - V3 planning (`Development` & `Design`) - V2 docs & tutorials (on primitives e.g. Tx Legos) - Bug-fixing & maintenance - Commence app learning & do project planning, so that we understand the composition of Rage/Sage - Plan roles & responsibilities and get interest for - UX Designer + Experiment Designer/Project Manager for Team Rage - Project Manager for Team Sage - Clean up dev environment