Squadron Process

Team Charter

Squadron Vision	We aspire to be the most fun, accessible, humble and passionate flight simulations squadron in the world
Mission	Hosting detailed, well thought-out, epic, serious fun, consistent BMS events Consider engagement with other sims Hosting training events and wiki Community outreach Open door Creating good relationships with community leaders, content creators Being the example of how 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 from idea funnel 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 Discord 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 Out: Website 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” - TBD for an alternative

Communication

We use Discord to communicate over voice, post and share events. We can also use TeamSpeak on demand at 74.91.123.42 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.

Planning

• We use a Trello Kanban board to manage our team work
• Each task (card) on the board represents a week of work or less
  • Bigger tasks can be broken down into multiple cards
• Patch members can add tasks they want to happen in the funnel
  • Patch members vote for the priority tasks
  • Patch members should get others to vote for their tasks and generally get consensus
  • Lead officers considers the squadron’s feedback and metrics, pulls tasks into the backlog
    • Items at the top should be worked on first
  • Patch members can/should work on tasks on their own initiative outside of the backlog if they want - we’re all volunteers here and no one is the boss :)
• Work happens continuously, and we meet every 2 weeks before the Saturday event to reassess our backlog, progress and what we can improve (See bi-weekly agenda and process)
• We discuss ongoing plans/work in #planning-and-strategy on Discord

Event Planning

Identify on a Trello card:

• Package commander: The guy who will lead the package.
• 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
    • Remote desktop, putting server in, saving mission etc
    • Running checklists, pre and post
    • Responsible for collecting metrics afterwards. Can be collected by backup moderator, but moderator ultimately responsible.
  • Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.
• Servers
  • Main: What is the primary server, and if its not documented how to maintain it, update the server documentation in this google doc
  • Backup: If the main is down.. What do we use?

Groups

Google

• Administered by groups.google.com
• Used for calendar invites, document on google
• UOAF-leadership can manage all groups

Uoaf-members

• 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

• Trello participation is included in this team membership here

Funding

UOAF uses a paypal business account under the email [[1]] .

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.

Servers

• We have the following temporary servers:
  • Lukrop’s
  • Bawki’s
  • Briland’s
• We need a more permanent solution.
• Specs required:
  • RAM: 16GB
  • Upload: 2mb/s * number of clients