Planning process for WMA Working Group

Exciting opportunity; being a member of the INCOSE WMA Agile Systems Engineering (SE) and Systems Architecture (SA) Working Group.
Charter is being worked. This will define the general goals and guidelines for the group.
In the meantime, there's the opportunity to practice what we've been teaching about the learning objectives of COPE; communication, decision making, leadership, planning, problem-solving, self-esteem, teamwork, and trust). These objectives won't be enough, though, because COPE assumes the group is geographically and temporally contiguous; the team is in the same place at the same time.
The WMA SE/SA working group is composed of people who can only rarely (if ever) all meet at the same place, and at the same time.

Consider the five (5) factors for teaming:

1. Team membership
2. Team assets
3. Shared vision
4. Shared values
5. Communication

Need to consider each in the context of the WMA working group.

Team membership:

1. Develop matrix of members
   
   1. name, email, phone number(s), social media references (LinkedIn, Facebook, Twitter, etc.), photo, city of residence (no addresses), meeting attendance history, interests (relevant to the working group), willingness to commit (and type/level of commitment), personal "pain points" (problems they would like to solve)
   2. Perhaps as Excel spreadsheet (better, an exportable database capable of supporting BLOBs [binary large objects])
   3. Limit each member's content to that which the member is willing to share (perhaps defer to a LinkedIn account).
   4. Guideline: what information would a member allow (want?) to be published in the Washington Post (or Times)? 
2. Ensure matrix is secured against unauthorized distribution and unauthorized use (e.g., encrypt the file)
   
   1. File-by-file encryption (e.g., 7-Zip) http://www.7-zip.org/
   2. Shared repository (e.g., VeraCrypt)
3. RASCI
   
   1. Consider responsibilities vs roles (e.g., Chairperson, Secretary, Morale Officer) and assign names to roles
      
      1. Chairs are: Dr. Subash Kafle, Shakila Khan & Daniel Canales
      2. Secretary TBD
      3. Others TBD
4. Partners
   
   1. GMU (https://getconnected.gmu.edu/organization/incosegmu)
   2. Chesapeake Chapter [Johns Hopkins University] (http://www.incose-cc.org/)
      
      1. 20160817 YouTube video [29:45]: Design Thinking 101 - INCOSE Chesapeake Chapter - 17Aug2016
      2. 20160927 YouTube video, Dr. David F. Rico [59:53]: Business Value of Agile Organizations - INCOSE Chesapeake Chapter - 27July2016

Team assets:

1. Information sharing
   
   1. WMA
      
      1. Website: http://www.incosewma.org/
      2. Goolge+ site:https://plus.google.com/111473200416971322260
      3. Events: http://www.incosewma.org/category/events/
      4. Event management: http://www.eventbrite.com/o/incose-wma-2550541684
      5. Twitter: https://twitter.com/incosewma
   2. WG meeting notices and notes
      
      1. GoogleGroups.com: https://groups.google.com/forum/#!forum/incose-wma-agile-sa-wg
   3. Content Management System (secured access to drafts, concurrent revision document control [to enable multiple sources to concurrently collaborate], editors with responsibility and authority to publish)
      
      1. Foundational documents (e.g., charter)
      2. Products (e.g., white papers, reference information)
      3. Forums
2. Webinar resources
   
   1. Skype
   2. WebEx
3. Expertise and experience
   
   1. Subject areas (Agile Systems Engineering, Software Architecture)
   2. Project management
   3. Meeting management
   4. Team development
   5. Planning

Shared vision: 

1. Charter (attached)
2. Plan

Shared values: 

1. Everyone has a day job and a family/social network. The working group can be no higher priority than #3.
2. Everyone is a professional with some value to add.
3. Everyone has some value they expect (need?) to receive as a result of being a member, perhaps a "personal painpoint" they need resolved.
4. Membership is peer-to-peer, equals among equals
5. Boundaries of intellectual property must be maintained to ensure honest and accurate attribution

Communication:

1. Frequency
   
   1. After meetings (notice and expectations; who owes what to whom by when [and why?])
   2. Before meetings (purpose, objectives, agenda [topics relevant to entire team except as noted, listed as questions the team needs to answer, estimated time with process for addressing], preparation for meeting (e.g., background and references), lead for each topic)
2. Form
   
   1. personalized email (each message is personalized)
   2. broadcast email (not personalized; includes newsletter)
3. Source
   
   1. Secretary (non-specific to readership)
   2. Personal relationship (one-to-many based on common values and interests)
   3. Professional relationship (one-to-many based on common goals)