Participation Team - Q3 Objectives and Key Results (2015)
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUVWXYZAAAB
1
Q3 Objectives and Key Results
2
Participation TeamStatus Aug 21Status Sept 11th
End of quarter evaluation
End of quarter commentsTEAM Comments
3
4
Objective 1Firefox OS Ignite Initiative has a great, validated community program designOn TrackOn Track80%This quarter's aim was to set up for a powerful participation program in FxOS in the future. That was achieved. Progress on having new contributors and foxfooders was substantially slowed by the existing state of participation in the FxOS project -- adding new contributors was premature and would have compromised quality and impact because of unclear contribution areas and opportunities and the state of the FxOS team.
5
KR1Long-term FirefoxOS community program designOn TrackOn Track100%Fx OS Participation team formed, full alignment on strategy and Q4 plan
6
KR250 weekly users of updated Foxfooding toolsOn TrackOn track80%We have an everage of 39 weekly users of existing foxfooding tools (ie. bugzillalite)
7
KR3100 weekly contributors on ‘beta’ community collaboration platformOn TrackMajor Change50%Getting alignment and clarity on dependencies took longer than planned. We now have a clear plan and roadmap for the first iteration of the platform (or Hub), set to go live on Nov 2
8
KR45 “test” events for in-person contribution and community buildingOn TrackOn Track150%8 events tested with lessons from Taipei and Philippines
9
10
Objective 2Mozilla and Firefox brand building efforts in Germany  boosted by larger and stronger communityAt RiskOn Track75%Overall, we are slightly behind but largely on-track for this objective in support of Mozilla's brand efforts, specifically around the November moment-in-time.
11
KR1Specific areas of contribution and participation measures defined jointly by participation and engagement teamsOn TrackAt Risk60%Only 5 of a desired 8 areas were clearly shaped with leadership roles and contribution opportunities
12
KR210 new community leaders/organizers recruitedAt RiskOn Track100%We have ~200 qualified leads (people we're communicating with actively), with 4 new leaders absolutely recruited.
13
KR3Events with a total of 1,000 attendees for the purpose of growing community and building issue supportAt RiskOn Track75%Prioritized piggybacking on existing events and having specific community recruiting methods/spaces (e.g. hacker lounge at Reject.JS). We didn't deliver on the ambition of testing 1-2 University-based events.
Keep in mind the timeframe for this extends to the end of October - Brian
14
15
Objective 3Our Indian community is successfully contributing to Fennec with “local” strategy in mindOn TrackOn Track50%There is a new core contributor driven product marketing team and campaign active for Fennec -- they are very well coordinated with product marketing/community marketing, testing new ideas, ramping up activity, and self-driven. The code contributor team that started with a substantial flurry of activity has gone dormant and the Fennec engineering team has not been able to prioritize support/mentorship.
16
KR1Contributors have shared goals and scope of work with community marketing, product marketing and Fennec teamsOn TrackOn Track50%Despite lost momentum towards the end for the coding part, we got a lot of the way here but short of writing code. Developers are signed up, a couple of leaders are invested (though lacking time), and the engineering team is actively thinking of ways to engage and integrate. - Brian
17
KR2Articulation of strategic opportunities/options for bringing local advantage to FennecOn TrackAt Risk25%Indian core contributor teams absolutely worked with a local lens, but are far from having a clear articulation of strategic opportunities.
18
19
Objective 4Systematize support for ReMo and communities of focusOn TrackOn Track90%This area was a success. Had 1:1 or group interactions (Vidyo/phone) with ~100 core contributors/community leaders, and gathered a detailed picture of 10 regional communities of focus. Lessons from this information will be synthesized shortly. Most important, the process for repeating information gathering (every 3 months), planning and coaching was systematized and is repeatable.
20
KR1ReMo + region/country of focus + partnership performance profile, dashboard and review process is developed and implementedOn TrackOn track100%
21
KR2Medium-term planning process in 3 communities is developed and testedOn Trackon track100%
22
KR3Coaching methods and process for community leaders is systematizedAt RiskAt risk75%Lots of research and practice, systematization of process. Have not synthesized or systematized the coaching methods.
23
24
Objective 5Launch the basics of a refreshed leadership development programOn TrackOn Track80%This area was a success, with the basics of a leadership development program in place. For "perfect" performance or over-performance, we would have wanted to have tested more of the workshops/curriculum more times and had a more detailed plan for the Leadership Summit.
25
KR1Basic first iteration of “Foundations of Mozilla” curriculum is developed and testedOn TrackOn Track80%"Beta" version of curriculum framework in place, with 5 workshops developed, 3 of them tested at least once.
26
KR2Volunteer selection for MozFest, Leadership Summit and Orlando Work Week is strategic and builds trust with volunteer communities, by designing, executing and systematizing a processOn TrackOn Track100%
27
KR3Outline and plan for a Leadership Summit to be held in late 2015 or early 2016On TrackOn Track70%This is firm, with solid concept in place. But only a rough and high-level plan of goals and agenda.
28
29
Objective 6Cross-Mozilla Participation Technology Group is formed and aligned on goals and key questionsOn TrackOn Track80%Recognize this objective was unclear as the language just reflected the cross-Mozilla group, even though the results involved a great deal of development on existing projects (achieved).
30
KR1Participation Technology Group is formed and trust is built through delivering a first draft of user stories and technology optionsOn TrackOn Track50%User stories developed and initial project for the group has been proposed. But the group has not yet met -- so can't say there's trust and/or alignment.
31
KR27 of 9 Mozillians next and Reps abstraction projects deliveredOn TrackOn Track80%6 of 7 projects to reinforce/extend existing participation tools (Mozillians, voting tool, reps, etc). Didn't deliver more because of unexpected code-debt.
32
33
TeamParticipation Team members are fired up about core contributor strategy and their rolesOn TrackOn Track100%Team performance and morale is high and trending upward. Every person has a clear short or long-term mandate, and the team overall has clear objectives.
34
KR1Team member mandates, objectives and key results are clearly articulated for Q3 and Q4On TrackOn Track100%
35
36
37
On Track
38
At Risk
39
Won't Happen
40
Major Change
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
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...
 
 
 
Team
George
Emma
Brian
William
Konstantina
Rosana
Guillermo
Rubén
Francisco
Lucy
Pierros
Giannis
Tasos
Nikos
TEMPLATE