Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a Raid Structure Template #109

Open
Seroxdesign opened this issue Mar 24, 2024 · 0 comments
Open

Create a Raid Structure Template #109

Seroxdesign opened this issue Mar 24, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed

Comments

@Seroxdesign
Copy link

Problem:

Our current process for Raids is not well document, but is similar to the following pattern:

Preparation:

  • RG Member/client brings in potential client
  • A conversation is had between Hunter/Cleric, and if there is alignment
  • Create a consultation via the RG site
  • Scope out and budget the work
  • Once a Cleric feels out the availability of a viable team, and the client commits
  • Client deposits fund into a smart escrow or a multisig provided by Raid Team

Kick off:

  • Raid party is assembled, typically with dev(s) and designer(s)
  • If party/project is big enough a Monk will also participate

Raiding:

  • Building is in process
  • Weekly meetings with client

Review:

  • Nearly finished product is delivered to the client
  • A review will commence, typically lasting 10-20% of total allotted time
  • Client is happy, signs off as completed

Wrap up:

  • Client releases funds
  • Raid Party does final hand off
  • Final meeting with client
  • Raid party splits the pay

Goal:

While the general outline of the process is defined, a few of the steps are not well documented and the process is typically on the raiding party. To improve Raid cohesion and address potential pitfalls we need to standardize our process (while leaving freedom to the party)

What we'd like to see is a template which covers the basic standards and processes around a Raid, for example:

  • The Raid Lifecycle: Steps for the Admin raiders to take (Clerics, Hunters, Monks) including consultation queues, client deposits, team formation, reviews, and payments on submission. This documentation will help us clarify what is included within a Raid to both the clients and non-admin raiders, as well as apply standards to admins.
  • Payment Guidelines: Documenting the base standard Raid financial process, for example most Raids have a cleric, and all Raids require a 10% tribute to spoils. This should be made clear to assist in Scoping and Billing, and to introduce clarity for clients. Additionally, Raiders will know when to expect their payments.

Consistency is key, by developing a proper template for Raids we can address many pain points and empower Raiders and Clients to deal with these issues.

@Seroxdesign Seroxdesign added documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed labels Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant