Squadron Process

From UOAF Codex
Revision as of 01:00, 12 January 2021 by Krause (talk | contribs)
Jump to navigation Jump to search

Team Charter

UOAF Roundel clean2.png

Squadron Vision We aspire to be the most fun, accessible, humble, and passionate flight simulation squadron in the world
Mission
  • Hosting detailed, well thought-out, epic, seriously fun, and consistent BMS events
  • Consider engagement with other sims
  • Host training events and wiki
  • Community outreach
    • Open door
    • Creating good relationships with community leaders, content creators
    • Being the example which sim communities should aspire to
  • Re-evaluation and re-assessment - data driven and collection
  • Frequent involvement of the squadron in squadron direction and decision making
Roles + responsibilities Lead (Krause)
  • Wringable neck for the squadron
  • Prioritizes backlog of work
  • Leads planning and squadron process as a servant leader
  • Veto power
  • Delegates powers to other patch members, and mentors/coaches them on execution
  • Expert-level flight sim guy

“Fellowship of the wing” (DF, Gus, Force)

  • Emeritus officers, serve as stakeholders for the squadron leadership
  • Advise current leadership but not decide anything

Roster (“patched members”):

  • Day to day moderators of the events/operations
  • Training
  • Flight leading
  • Package leading
  • Responsible for supporting and improving SOPs
  • Face of the squadron
  • Meet minimum competencies
    • Sharing resources to help people get to min competencies
  • Giving input and voting on what we should do next
  • Fragging/supporting events
  • Event coordination (See below)

Frag team:

  • Owns standards for the frag
    • Improving and teaching those standards
  • Generating the frags
Scope In:
  • BMS events
  • Open to other types of gaming (e.g. DCS, IL2, Steelbeasts etc)
    • Our values should apply to those games
  • Cross-community events
  • Content creation
    • Mod development
    • Videos
  • Creating/supporting a wiki (resurrect codex)
  • Everything on Discord
  • Surveying and collecting metrics
  • Server maintenance/expansion
  • Website

Out:

  • TeamSpeak (We can use it, but we want to move toward discord)
Values
  • Mutual learning
  • Being respectful
  • Be an example to others
  • Serious fun
  • Team work
  • Should accept/give feedback
  • Expertise
  • Continuous improvement
  • Punctuality
Success criteria How do we know if we are being successful?
  • We have a set of KPIs here which are collected after every event. We use this data to steer improvements in the squadron.
Risks/weaknesses
Motto Sordida Unguibus “Dirty fingernails”

Communication

We use Discord (click to join) to communicate over voice, post and share events. We can also use TeamSpeak on demand at 87.127.93.6 pw: grits.

Documents

Please store all documents (including ACMI) on the UOAF google drive here. Note that this is a public folder, but can only be edited by the UOAF members google group which includes all patched members. IF you want to restrict access (e.g. confidential info), be sure to click the “share” button on the top right and tweak it so that only uoaf-members@googlegroups.com OR a specific subset of members can see it.

Planning

  • We use a Trello Kanban board to manage our team work
  • We use #event-and-squadron-planning discord channel to discuss plans and who is running events, and put work up on Trello
  • We use #metrics-and-event-performance to share back performance from events

Event Planning

Identify on a Trello card:

  • Package commander: The guy who will lead the package. Now on the signup sheet, used to be on Trello.
  • Mission fragger: Make the mission, test it, upload it to drive. Collaborate with others (especially package commander) to ensure quality. Make briefing and posting it.
  • Event team
    • Event Coordinator: Responsible for making sure the entire event is executed on time, with quality and overall delivery of the event.
      • Making sure software and dependencies are up to date on the server
    • Moderator: Responsible for running the event from a logistics point of view
    • Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.

Groups

Google

Uoaf-members aka uoaf-members@googlegroups.com

  • Who: All patch members.
  • Have edit access to the google drive location (all can view)
  • Includes “UOAF-leadership” (see below)

UOAF-leadership

  • Who: Officers/leadership team

Trello

Funding

UOAF uses a paypal business account under the email uoafdonations@gmail.com

The paypal link for recurring monthly is here. Members and stakeholders are suggested to donate to ensure continued operation of the squadron.

The paypal account is currently owned by Chris Krause. Any balance is held in reserve for voting by the squadron, any deficit is currently paid for out of pocket by Chris Krause.

Financial records of the paypal are to be shared with the community whenever requested.

Voting in Patched Members

Anyone can initiate a vote for someone to become a patched member. The goal of voting is to gain consensus on whether or not the person in question exemplifies the values of UOAF (see above) and also is taking on the list of responsibilities of a patched member on his/her own initiative (See above), with promise to expand those responsibilities.

We bias toward saying "No" than "Yes" and hold a very high personal conduct bar. Anyone who we can't say no to should have been a patch member already!

The squadron leader has veto power as with all things.

Initiating a Vote

Make a post in #roster-voting, following the template: 

@Roster I'd like to nominate [@name] for roster! 
[optional reason for nomination]
Respond to this with :goodvibes:  if you think [he/she] should be one and :Disappointed:  if not.

Then send an email to uoaf-members@googlegroups.com letting everyone know a nomination is starting. This is to give members who are not monitoring discord a chance to see the notification, and to make sure it doesn't get buried.

After 72 hours if complete consensus is made, the squadron leader or a designated 2nd will reach out to the individual and invite them to the roster - if they accept, we add them to the Discord @roster tag and make a hype post in #roster with mad emoticons.

Remember that they will need to be added to the Google group (Can be done by any leadership), and should also review and understand this page here on the Codex.

Onboarding Roster Checklist

Offboarding Roster Checklist

  • Remove from google group
  • Remove Roster tag
  • Remove from Trello team
  • Remove AWS IAM account (if applicable)

Servers

    • Server database is maintained here
    • There is also a link with credentials/RDP information in it, ask leadership for a link.
Retrieved from "http://codex.uoaf.net/index.php?title=Squadron_Process&oldid=7574"