Engagement/Dev Marketing Durable Team: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(first edit on Mozilla wiki - adding myself to durable team!)
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Overview ==
== Overview ==
We're the '''Dev Marketing Durable Team''' and our goal is to build and grow our developer marketing program!
We're the '''Dev Marketing Durable Team'''. We are a "durable" (aka Agile) team within Marketing, focused on engaging with developers. Our charter is to increase the visibility and perception of Mozilla with developers, highlight the great products and technology work going on at Mozilla, and help our engineering teams increase their reach and impact as they engage with developers. We run campaigns, create content, host events, and build community, with lots of help from Developer relations, Platform and Firefox teams.


==Key Initiatives==
==Key Initiatives & Deliverables==
===Q3 2016===
'''Initiative 1:''' Establish value proposition for web developers & designers to build, test and debug websites and web apps across browsers
 
Deliverables:
* Go To Market plan for Web Compatibility
* Define and scope core audience problems
* Write value propositions and messaging
* Create test plan
'''Initiative 2:''' Showcase Technology Leadership and Innovation at Mozilla
 
Deliverables:
*View Source Conference Berlin in September, 400 attendees (cancelled View Source Seattle)
*Establish web and web app compatibility value proposition with developers
===Q2 2016 [Revised]===
* Targeted developers identify Mozilla as a tech leader
* Web developers build web sites and apps that are compatible with Firefox
===Q1 2016===
===Q1 2016===
* Smarter, Targeted Developer Marketing, coordinated across product/engineering and functional teams
* Smarter, Targeted Developer Marketing, coordinated across product/engineering and functional teams
Line 12: Line 28:
* Build a broader/deeper developer community with ongoing touchpoints
* Build a broader/deeper developer community with ongoing touchpoints


===Q2 2016 [Revised]===
==Launched Projects (Public)==
* Targeted developers identify Mozilla as a tech leader
===[http://www.viewsourceconf.org View Source 2016 - Berlin]===
* Web developers build web sites and apps that are compatible with Firefox
* [https://www.youtube.com/watch?v=Dl6qKLhufHY&feature=youtu.be View Source Promotional Teaser Video]
* [http://igniteberlin.com/ View Source - Ignite Call for Papers]
* [https://twitter.com/viewsourceconf View Source on Twitter]
===Browser Compatibility===
* [https://hacks.mozilla.org/2016/07/make-the-web-work-for-everyone/ "Make the Web Work for Everyone" - Mozilla Hacks Post]
* [https://news.ycombinator.com/item?id=12042767 Hacker News Commentary on Compat Post]
* [https://drive.google.com/file/d/0BzHULT8I_KE6bVNTV0xqSThKQVU/view Web Compatibility Message Testing on Facebook and Twitter]
* [https://storify.com/mozilla/designing-a-web-for-everyone "Designing a Web for Everyone" Twitter Chat]
* [https://hacks.mozilla.org/2016/08/a-web-for-everyone-interviews-with-web-practitioners-rachel-andrew "A Web for Everyone: Interviews with Web Practitioners — Rachel Andrew" - Hacks Blog Post]
 
===[https://medium.com/mozilla-tech Mozilla Tech - A Medium Channel]===
===[https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/ "Shipping Rust in Firefox" - Mozilla Hacks Blog]===
 
== Team ==
We are a cross-functional team within the Marketing organization, with skill sets comprising product marketing, brand, creative, events, social media, community, project management, and more.
 
* Ali Spivak (Product Owner)
* Lizz Noonan (Scrum Master/PM)
* Alex Costello (Scrum Process Support)
* Arcadio Lainez (Marketing Manager)
* Alex Klepel (Communications Lead)
* Bradley Cohen (Audience Strategy)
* Ryan Pollock (Product Marketing)
* Lee Tom (Design Lead)
* Sandra Persing (Event Strategy and Production)
* Justin Crawford (Growth Lead/Dev Expert)


== Team Documents and Tools ==
== Team Documents and Tools ==
Line 23: Line 64:
* [mailto:devmarketingdt@mozilla.com Team mailing list] and [https://groups.google.com/a/mozilla.com/forum/?hl=en#!forum/devmarketingdt discussion archive]
* [mailto:devmarketingdt@mozilla.com Team mailing list] and [https://groups.google.com/a/mozilla.com/forum/?hl=en#!forum/devmarketingdt discussion archive]
* [irc://irc.mozilla.org/devmarketing #devmarketing] IRC channel
* [irc://irc.mozilla.org/devmarketing #devmarketing] IRC channel
* [https://docs.google.com/spreadsheets/d/1Qo5d4knm3mfjjqZeRGZRdhEEDV_bdW7As5GiRiXM3us/edit?usp=sharing Team member detailed schedule]
===Taiga Taskboards===
{{Admon/note|NOTE:|Replaced Kanbanery beginning Q2 Sprint 2}}.
*[https://tree.taiga.io/project/lmn0p-dev-marketing-durable-team/taskboard/q3s2 Q3 Sprint 2] <br>
*[https://tree.taiga.io/project/lmn0p-dev-marketing-durable-team/taskboard/q2-sprint-4 Q3 Sprint 1] <br>
*[https://tree.taiga.io/project/lmn0p-dev-marketing-durable-team/taskboard/q2-sprint-3 Q2 Sprint 3] <br>
*[https://tree.taiga.io/project/lmn0p-dev-marketing-durable-team/taskboard/sprint-2-2028 Q2 Sprint 2]
== Three Week Sprint Schedule ==
{{Admon/important|Beginning in Q2 2016, we switched from two to three week sprints. The new schedule is below.}}
'''Q2 Sprint 1 begins on THURSDAY, APRIL 21.'''
{| class="wikitable"
|-
! Meeting/Event !! Time and Days !! Attendees !! Notes
|-
| Sprint Planning Meeting || Every first Thursday, 9am - 12pm PT (first day of a new sprint) || Core Team is required|| Stakeholders may listen in, This meeting lasts as long as it takes. This is the first day of a new sprint.
|-
| User Story Readouts || Every first Thursday, 11 - 11:45am PT || PO, PM, Sponsor, Marketing Leads required || All teams have 5 minutes each to read out their User Stories for that sprint, followed by a Q&A with Leads.
|-
|Homeroom Day || Every first Friday, all day || All Durable Team members || Discretionary day - can be used to finalize sprint planning or prepare for sprint work beginning Monday. Also time for functional teams to meet and to have meetings that fall outside the purview of the Durable Team.
|-
| Daily Stand-Ups (15 minutes only) || 1st Monday through 3rd Tuesday of Sprint, Daily at 9:30am PT || Core Team is required || Anyone is welcome to listen, but may not speak, take all questions offline to Ali, Alex or Lizz.
|-
| Sprint Demo Meeting || Every third Wednesday (last day of Sprint), time TBD|| Everyone is welcome || This is where we show the work completed in the sprint, it's a place to ask questions and give feedback. In Q2, all Durable Teams will be demoing to the full Marketing organization. Time TBD - first Q2 sprint demo is May 11.
|-
| Sprint Retrospective Meeting || Every third Wednesday (last day of Sprint), time TBD || Core Team Only || No One else is invited to this meeting! We will discuss what to start, stop and continue doing in the next sprint.
|}
* All Meetings are in Elizabeth (Lizz) Noonan's Vidyo
* if you have questions about these meetings, please contact Lizz Noonan


== Standup Recordings ==
== Standup Recordings ==
Line 66: Line 140:


===Q2 2016===
===Q2 2016===
 
Sprint 1
== Three Week Sprint Schedule ==
*[https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=vKaqqWC5S5gsmrI Wednesday, April 27]
{{Admon/important|Beginning in Q2 2016, we switched from two to three week sprints. The new schedule is below.}}
 
'''Q2 Sprint 1 begins on THURSDAY, APRIL 21.'''
 
{| class="wikitable"
|-
! Meeting/Event !! Time and Days !! Attendees !! Notes
|-
| Sprint Planning Meeting || Every first Thursday, 9am - 12pm PT (first day of a new sprint) || Core Team is required|| Stakeholders may listen in, This meeting lasts as long as it takes. This is the first day of a new sprint.
|-
| User Story Readouts || Every first Thursday, 11 - 11:45am PT || PO, PM, Sponsor, Marketing Leads required || All teams have 5 minutes each to read out their User Stories for that sprint, followed by a Q&A with Leads.
|-
|Homeroom Day || Every first Friday, all day || All Durable Team members || Discretionary day - can be used to finalize sprint planning or prepare for sprint work beginning Monday. Also time for functional teams to meet and to have meetings that fall outside the purview of the Durable Team.
|-
| Daily Stand-Ups (15 minutes only) || 1st Monday through 3rd Tuesday of Sprint, Daily at 9:30am PT || Core Team is required || Anyone is welcome to listen, but may not speak, take all questions offline to Ali, Alex or Lizz.
|-
| Sprint Demo Meeting || Every third Wednesday (last day of Sprint), time TBD|| Everyone is welcome || This is where we show the work completed in the sprint, it's a place to ask questions and give feedback. In Q2, all Durable Teams will be demoing to the full Marketing organization. Time TBD - first Q2 sprint demo is May 11.
|-
| Sprint Retrospective Meeting || Every third Wednesday (last day of Sprint), time TBD || Core Team Only || No One else is invited to this meeting! We will discuss what to start, stop and continue doing in the next sprint.
|}
 
* All Meetings are in Elizabeth (Lizz) Noonan's Vidyo
* if you have questions about these meetings, please contact Lizz Noonan
 
== Team ==
We are a cross-functional team within the Marketing organization, with skill sets comprising product marketing, brand, creative, events, social media, community, project management, and more.
 
* Ali Spivak (Product Owner)
* Lizz Noonan (Scrum Master/PM)
* Alex Costello (Scrum Process Support)
* Arcadio Lainez (Marketing Manager)
* Alex Klepel (Comms Lead)
* Bradley Cohen (Audience Strategy/Interim Platform PMM)
* Lee Tom (Design Lead)
* Sandra Persing (Event Lead)
* [[User:Jswisher|Janet Swisher]] (Dev Community Manager)
* Justin Crawford (Growth Lead/Dev Expert)
* Brent Walter [part-time] (Email and CRM Support)

Latest revision as of 21:36, 9 September 2016

Overview

We're the Dev Marketing Durable Team. We are a "durable" (aka Agile) team within Marketing, focused on engaging with developers. Our charter is to increase the visibility and perception of Mozilla with developers, highlight the great products and technology work going on at Mozilla, and help our engineering teams increase their reach and impact as they engage with developers. We run campaigns, create content, host events, and build community, with lots of help from Developer relations, Platform and Firefox teams.

Key Initiatives & Deliverables

Q3 2016

Initiative 1: Establish value proposition for web developers & designers to build, test and debug websites and web apps across browsers

Deliverables:

  • Go To Market plan for Web Compatibility
  • Define and scope core audience problems
  • Write value propositions and messaging
  • Create test plan

Initiative 2: Showcase Technology Leadership and Innovation at Mozilla

Deliverables:

  • View Source Conference Berlin in September, 400 attendees (cancelled View Source Seattle)
  • Establish web and web app compatibility value proposition with developers

Q2 2016 [Revised]

  • Targeted developers identify Mozilla as a tech leader
  • Web developers build web sites and apps that are compatible with Firefox

Q1 2016

  • Smarter, Targeted Developer Marketing, coordinated across product/engineering and functional teams
  • Developer Events
  • Developer Email Program/CRM
  • Build a broader/deeper developer community with ongoing touchpoints

Launched Projects (Public)

View Source 2016 - Berlin

Browser Compatibility

Mozilla Tech - A Medium Channel

"Shipping Rust in Firefox" - Mozilla Hacks Blog

Team

We are a cross-functional team within the Marketing organization, with skill sets comprising product marketing, brand, creative, events, social media, community, project management, and more.

  • Ali Spivak (Product Owner)
  • Lizz Noonan (Scrum Master/PM)
  • Alex Costello (Scrum Process Support)
  • Arcadio Lainez (Marketing Manager)
  • Alex Klepel (Communications Lead)
  • Bradley Cohen (Audience Strategy)
  • Ryan Pollock (Product Marketing)
  • Lee Tom (Design Lead)
  • Sandra Persing (Event Strategy and Production)
  • Justin Crawford (Growth Lead/Dev Expert)

Team Documents and Tools

Taiga Taskboards

Note.png
NOTE:
Replaced Kanbanery beginning Q2 Sprint 2

.

Three Week Sprint Schedule

Important.png
Beginning in Q2 2016, we switched from two to three week sprints. The new schedule is below.

Q2 Sprint 1 begins on THURSDAY, APRIL 21.

Meeting/Event Time and Days Attendees Notes
Sprint Planning Meeting Every first Thursday, 9am - 12pm PT (first day of a new sprint) Core Team is required Stakeholders may listen in, This meeting lasts as long as it takes. This is the first day of a new sprint.
User Story Readouts Every first Thursday, 11 - 11:45am PT PO, PM, Sponsor, Marketing Leads required All teams have 5 minutes each to read out their User Stories for that sprint, followed by a Q&A with Leads.
Homeroom Day Every first Friday, all day All Durable Team members Discretionary day - can be used to finalize sprint planning or prepare for sprint work beginning Monday. Also time for functional teams to meet and to have meetings that fall outside the purview of the Durable Team.
Daily Stand-Ups (15 minutes only) 1st Monday through 3rd Tuesday of Sprint, Daily at 9:30am PT Core Team is required Anyone is welcome to listen, but may not speak, take all questions offline to Ali, Alex or Lizz.
Sprint Demo Meeting Every third Wednesday (last day of Sprint), time TBD Everyone is welcome This is where we show the work completed in the sprint, it's a place to ask questions and give feedback. In Q2, all Durable Teams will be demoing to the full Marketing organization. Time TBD - first Q2 sprint demo is May 11.
Sprint Retrospective Meeting Every third Wednesday (last day of Sprint), time TBD Core Team Only No One else is invited to this meeting! We will discuss what to start, stop and continue doing in the next sprint.
  • All Meetings are in Elizabeth (Lizz) Noonan's Vidyo
  • if you have questions about these meetings, please contact Lizz Noonan

Standup Recordings

Q1 2016

Sprint 1

Sprint 2

Sprint 3

Sprint 4

Q2 2016

Sprint 1

Retrieved from "https://wiki.mozilla.org/index.php?title=Engagement/Dev_Marketing_Durable_Team&oldid=1147340"