The Swarm Template has been used for the past 6 months to kickstart projects by swarms. For a variety of reasons, swarms have not always kept the template up to date, resulting in missed important milestones, specifically Research and Specification. These milestones have often been skipped or overlooked before engineering implementation has begun.
Upon reflection on the types of work being done inside swarms, it can be concluded that a Swarm ITSELF shouldn’t be going through milestones. Rather, projects WITHIN Swarms should be the ones going through regular milestones. Having a single “Specification” or “Ideation” phase for an entire swarm should not allow for carte blanche development from then on. For example, the Keycard swarm should have multiple milestones for each of the sub-swarms (e.g. multi-account) rather than one milestone for the entire Keycard swarm. Therefore, Research/Specification milestones should be a semi-regular occurrence for all Swarms across multiple projects, not one-off events.
For those interested in helping to contribute or give feedback on the existing process, feel free to discuss your thoughts below. Specifically, the following questions are top of mind for the Janitors:
- What are ‘frictionless’ ways we can improve the Swarm process to ensure the Research and Specification milestones are completed?
- Do you have examples of a review/gating mechanism being done effectively in similar organizations (e.g. similar size, distributed, web3, etc.)