Changes between Initial Version and Version 1 of org/meetings/2017Amsterdam/Notes/VegasTeamsandBeyond


Ignore:
Timestamp:
Mar 27, 2017, 1:09:41 PM (2 years ago)
Author:
alison
Comment:

added session notes

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Amsterdam/Notes/VegasTeamsandBeyond

    v1 v1  
     1== Vegas Teams: what they do, what they don't do ==
     2
     3Notes from the session "Roger explaining Vegas teams", Sat 3/25,
     43:30pm-16:30
     5
     6
     7
     8Brief history of vegas teams. Mike and Roger locked up in a room and
     9thought about team structure.
     10
     11
     12
     13More or less a person per product + "org team"+ press team
     14
     15
     16
     17Later: UX team, Community team.
     18
     19
     20
     21Project manager also member of Vegas teams (Isa)
     22
     23
     24
     25Problem at the beginning was, that Vegas teams are kind of "managers"
     26without wanted to be "managers" bc this has negative associatiosn.
     27
     28
     29
     30Historically these were called "advocates", but it was kind of tricky.
     31
     32
     33
     34Originally the job of vegas teams was to coordinate needs/requirements
     35between different teams.
     36
     37
     38
     39Shari wanted have it more: "Team A tells team B what they need". (in
     40contrast to "Team A did X"-style report backs)
     41
     42
     43
     44Current structure: Weekly IRC meeting. More an "operations meeting".
     45
     46
     47
     48Small excursus: how funding within Tor works and how the tasks are assigned
     49to the right people.
     50
     51
     52
     53Request from group to have regular 1:1 with at least team leads
     54
     55
     56
     57Plus have reguar coordination meeting.
     58