Stewards Analysis
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNOPQRST
1
Stewards Analysis for 2012 Planning
2
3
Summary
4
There are 39 functional areas covered, with over 70 Stewards and over 500 contributors registered for all areas
5
Community building capacity of organization is lower than anticipated (13% of functional areas high capacity, 51% medium, 36% low)
6
Several teams have potential for high capacity in the short-term but lack community manager resources (QA, Coding, Webdev, l10n, Metrics, Accessibility)
7
Several teams have lost capacity over time (eg, both Legal and Security have history of volunteer participation but are not as active today)
8
9
Recommendation
10
Short-term opportunities for increasing capacity should focus on QA, Coding, Identity, Engagement, L10n, Metrics
11
We should run campaigns about using the Phonebook to drive additional sign-ups and usage of group tags, location and other data fields
12
13
14
Functional AreaCapacityDefined opportunitiesMapped pathsHealth targets setRegistered contributorsTeam tagNotes
15
AccessibilityMYYY7accessibilityWould be high capacity if there were dedicated community building resources on team.
16
AddonsHYYY35addons, add-ons
17
AppsLNNN18apps
18
AutomationMYYY19automation, a-teamThis includes 3 different automation teams (QA automation, tools automation, build automation) and there is differing capacity across teams.
19
BizdevLNNN--
20
CodingMYYY68firefoxWould be high capacity if there were dedicated community building resources on team.
21
CreativeMNNY--
22
DocumentationMNYN10developer documentation
23
DevToolsMYNY3devtools
24
Engineering PMLNYY--
25
FinanceLNNN--
26
FundraisingMYNY--
27
GraphicsMYYY8graphics
28
IdentityMYYY6identity
29
InfraSecMYYY--
30
LabsLNNN24labsLabs is going through a reboot (see David's notes in Stewards/Labs page)
31
LegalLNNN--Legal did just finish the MPL rewrite as a contributor-based project but that was driven by Luis who is no longer an employee.
32
L10nMYYY18l10nWould be high capacity if there were dedicated community building resources on team.
33
Market InsightsLNNN--
34
MetricsLNNN4metricsLots of potential for group (for instance, launching the public Metrics dashboard)
35
MobileMNNN28mobileSome existing community building activity (such as Mobile Test Drivers) is underway but hasn't been captured by Stewards
36
PancakeLNNN4pancake
37
PeopleLNNN--
38
PrivacyLNNY7privacy
39
Product MarketingMNNN3product marketingSome existing community building activity is underway but hasn't been captured by Stewards
40
PRHYYY7communications
41
QAMYYY27qaWould be high capacity if there were dedicated community building resources on team.
42
Research/B2GLNNN7research, b2g
43
RecruitingLNNN--
44
SecurityMYNN24securitySecurity has a long history of volunteer contributions that can be leveraged.
45
ServicesMYNY18services
46
SupportHYYY18support
47
Systems AdminMNNN28systems administration, ITSome existing community building activity is underway but hasn't been captured by Stewards
48
ThunderbirdMYYY35thunderbirdWould be high capacity if there were dedicated community building resources on team.
49
User EngagementHYYY11user engagement
50
User ResearchMNNN--Some existing community building activity (such as Test Pilot as an entry point for casual contributors) is underway but hasn't been captured by Stewards
51
UXLNNN10ux
52
WebdevMYYN36webdevWould be high capacity if there were dedicated community building resources on team.
53
WebFWDHYYY25webfwd
54
55
Thoughts on how to improve this
56
* Rename to Contribution Scorecard?
57
* Have column to track dedicated Community Manager for teams?
58
* Have column to track audience (new vs active) or which areas are good entry points vs. which are good for existing contributors?
59
* Add other variables suggested in audit? See slides 33-41 for Scorecard recommendations
60
** A map or list of activities volunteers can engage in
61
** How it will measure the number of contributors involved in these tasks
62
** How it will measure the average response time a contributor waits for any decision from Mozilla
63
** Where its documentation and processes live for on-ramping new members
64
** How it will assess when a contributor stops participating
65
** How it will try to reach out to a contributor who stops participating and ask them why
66
** A defined process for thanking/acknowledging contributors
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...