---
# System prepended metadata

title: 'Dragon''s Lair: 3/24/2022'
tags: [' project management', ' dragons', v3]

---

---
tags: v3, dragons, project management
---

# Dragon's Lair: 3/24/2022

## Agenda

* Gather feedback on Planning meeting
* Review Invisible Suburbs Kanban board
* Close out Issues in Done
* Align on priorities for next week
* Discuss any new issues
* Prioritize ready column

## Notes

- Continue to emphasize that we're willing to change and iterate based on feedback as we go
- Retro meeting next week will be a good example of this as well
- Our planning sessions can be improved
    - Too many folks in the planning meeting
    - Can we break these up? 
    - Engage everyone -- start with design, move to dev, etc.
    - This would also mirror our process -- start with design tickets first
    - Start with the Design lane and then move through the other tickets
- What makes sense for Design to present during these planning meetings?
    - Do they want to solicit opinions? Keeping to a time limit -- feedback could balloon and take up too much time
    - Focusing on things that are in production and are closest to handoff
- To limit size of meeting, should we switch to a different channel when our meeting starts?
- Schedule specific roadmap meeting to allow for distinction
- Are roadmap and product their own meetings?
    - Let's bring this back up -- Roadmap meetings every other week
    - If the meetings are back-to-back folks will stay and listen 

## Show & Tell

- Something can't be demo'd until it's *Done*
- Do we want to include a tag for the demo date?
- Keep an eye on how folks are feeling as they're getting work done
- Define testing process

## Action Items

- [ ] Define testing process (as a starting point)
- [ ] Continue to adding docs to the Wiki
- [x] Add Rage Reports to the Wiki
- [x] Think through RG cohort about Solidity reviews (peer reviews) - jp
- [ ] jp and Sam to go through the contract docs prior to audit