Engagement/Mozilla.org Durable Team: Difference between revisions

Latest revision as of 16:03, 27 June 2018

Overview

Mozilla.org Durable team

- Who we are, how we work and what we do:

Who we are: The mozilla.org durable team consists of team members from multiple functional domains: UX, Copy writing, Front End Development, Back End Development, plus the Product Owner and Scrum Master. The durable team is an agile one, meaning that we use agile practices (a scrum implementation of the agile methodology) to produce 'potential shippable' work within the time box of each sprint.

What we do: We work on the mozilla.org website creating and publishing new designs and content; ensuring the security of visitors to the site; conveying the messaging of the Mozilla Foundation and the Mozilla Corporation which produces the Firefox web browser and other technologies.

How we work: In short, we work based on user stories that intend to address user needs and wants. [The formula for writing user stories is: "As a user (persona), I want to (do such thing) so I can (derive some benefit)]. When we have enough information to support the validity of a given user story, we move to creating the benefit for the user. User stories may warrant direct input/work by all domains of functional expertise that are defined in the team's make up, as listed above. Some user stories may require only one such domain expert. Given the nature of the work and the mozilla.org 'product' itself, creative design can be weighted heavily in a given user story. In some circumstances, the acceptance criteria defined by the Product Owner can result in a 'research' story, in which, for one example, the resulting output will be one or more prototypes intended for real user testing. The resulting feedback helps define the direction in which mozilla.org will be taken to best suit user wants and needs, which is the ultimate goal.

--- 2017 / Q1 Key Results

Test the hypothesis that a universal navigation increases PPV by 10% by deploying 2-3 navigation prototype tests live on moz.org and/or MDN
Publish Internet Health Privacy & Security sub-page on mozilla.org by January 20th (DONE)
Increase download conversion on paid ad funnel to ~15% (from 8% today) by optimizing download page to match acquisition campaign messaging (DONE)
Implement new visual identity to at least one key page/element (Blog template, cross-site nav)
Publish CSS Grid landing page on mozilla.org by March 16th

2016 / Q4 Key Results

Placeholder . . .

Key Q3 2016 Initiatives -

New homepage that demonstrably improves visitors’ understanding of what Mozilla does and believes, pushed live to at least 50% of the audience

(Status on 8/19 - done, to 100% of audience).

Implement landing page for the Technology pillar

Key Q2 2016 Initiatives - (to be posted)

Key Q1 2016 Initiatives

Improve newsletter email conversion on mozilla.org
Improve conversion on the Firefox download page (/new)
Improve Firefox desktop onboarding and testing process
Rebrand www.mozilla.org

Relevant Links

--

Kanban Board for Sprints (deprecated)

2 Week Sprint Meetings

Template:Admin/note

Meeting	Time and Days	Attendees	Notes
Stand-up & Project Review	Mondays, 9-9:30 am PT. In-person (Eric Renaud's Vidyo room).	Core Team is required	Anyone is welcome to listen, but may not speak, take all questions offline to David and/or Eric.
Stand-up	Tuesdays and Thursdays, 9-9:15 am PT. In-person (Eric Renaud's Vidyo room).	Core Team is required	Anyone is welcome to listen, but may not speak, take all questions offline to David and/or Eric.
Team Time	Wednesdays, 9:15 - 10 am PT. In-person (Eric Renaud's Vidyo room).	Core Team is requested, Team only	No agenda, though the time slot may be leveraged for specific work, discussions or presentations.
Sprint Demo Meeting	Every third Wednesday (last day of Sprint), time TBD	Everyone is welcome	This is where we celebrate by showing the work completed in the sprint; it's a place to ask questions and give feedback. In Q2, all Durable Teams will started demoing to the full Marketing organization. In Q3, Functional Teams started showing their work in the Sprint Demo on a regular basis.
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 Eric Renaud's Vidyo
if you have questions about these meetings, please contact Eric

Team

Alex Gibson (Front-End Developer)
Craig Cook (Front-End Developer)
David Tenser (Team Lead)
Eric Renaud (Program Manager)
Jeffrey Taylor (Content Strategist)
Jennifer Rouse (UX designer)
Jon Petto (Front-End Developer)
Mark Weaver (Designer)
Michael McCombie (Product Designer)
Raphael Raue (SEO)
Stephanie Hobson (Front-End Developer)
Vince Joy (UX/UI)

@@ Line 1: / Line 1: @@
 == Overview ==
-{{admon/note|Current sprint April 25th - May 11.}}
+'''Mozilla.org Durable team'''
-We are the '''Mozilla.org Durable team''' (aka the Rock).
+- Who we are, how we work and what we do:
+Who we are: The mozilla.org durable team consists of team members from multiple functional domains: UX, Copy writing, Front End Development, Back End Development, plus the Product Owner and Scrum Master. The durable team is an agile one, meaning that we use agile practices (a scrum implementation of the agile methodology) to produce 'potential shippable' work within the time box of each sprint.
+What we do: We work on the mozilla.org website creating and publishing new designs and content; ensuring the security of visitors to the site; conveying the messaging of the Mozilla Foundation and the Mozilla Corporation which produces the Firefox web browser and other technologies.
+How we work: In short, we work based on user stories that intend to address user needs and wants. [The formula for writing user stories is: "As a user (persona), I want to (do such thing) so I can (derive some benefit)]. When we have enough information to support the validity of a given user story, we move to creating the benefit for the user. User stories may warrant direct input/work by all domains of functional expertise that are defined in the team's make up, as listed above. Some user stories may require only one such domain expert. Given the nature of the work and the mozilla.org 'product' itself, creative design can be weighted heavily in a given user story. In some circumstances, the acceptance criteria defined by the Product Owner can result in a 'research' story, in which, for one example, the resulting output will be one or more prototypes intended for real user testing. The resulting feedback helps define the direction in which mozilla.org will be taken to best suit user wants and needs, which is the ultimate goal.
+---
+/ Q1 Key Results
+* Test the hypothesis that a universal navigation increases PPV by 10% by deploying 2-3 navigation prototype tests live on moz.org and/or MDN
+* Publish Internet Health Privacy & Security sub-page on mozilla.org by January 20th (DONE)
+* Increase download conversion on paid ad funnel to ~15% (from 8% today) by optimizing download page to match acquisition campaign messaging (DONE)
+* Implement new visual identity to at least one key page/element (Blog template, cross-site nav)
+* Publish CSS Grid landing page on mozilla.org by March 16th
+/ Q4 Key Results
+* Placeholder . . .
+Key Q3 2016 Initiatives -
+* New homepage that demonstrably improves visitors’ understanding of what Mozilla does and believes, pushed live to at least 50% of the audience
+(Status on 8/19 - done, to 100% of audience).
+* Implement landing page for the Technology pillar
+Key Q2 2016 Initiatives - (to be posted)
 Key Q1 2016 Initiatives
@@ Line 13: / Line 38: @@
 == Relevant Links ==
+* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=mozilla.org%20needs%20triage&sharer_id=148348&list_id=13176101 The Source of Truth (Bugzilla)]
 * [https://docs.google.com/spreadsheets/d/18B2qCee5paSE3l76SxK_89rtfkqmdtmhVqrOEOHdXcE/edit#gid=0 Product Backlog]
-* [https://tree.taiga.io/project/malexis-mozillaorg-durable-team/taskboard/sprint-1-5059 Current sprint task board]
+* [https://tree.taiga.io/project/malexis-mozillaorg-durable-team/backlog Taiga PBL & links to sprint task boards]
-* [https://mozilla.kanbanery.com/projects/66737/board/?key=1df7dec4598f97a4372421de2bc38836702367f9 Kanban Board for Sprints (deprecated)]
+* [http://www.standu.ps/project/www Asynchronous daily stand ups (Tuesdays & Thursdays)]
 * [https://docs.google.com/presentation/d/1RQ1VIROgO1vqQbUOXvmn1S53Viguc-CLG_D_CRKlMl4/edit#slide=id.gedf8b9d23_0_11 Agile Playbook]
-* [[/Standups|Daily Standups]]
 * [[/Testing_Playbook|Testing Playbook]]
 * [https://docs.google.com/document/d/1ZkOpvPUNmncw1009mL-KIwY7ztS22A_OmpBwfI7NWfw/edit Optimizely training notes]
 * [[/Retrospectives|Retrospectives]]
 * [[/Sprint_Demos|Sprint Demos]]
+--
+* [https://mozilla.kanbanery.com/projects/66737/board/?key=1df7dec4598f97a4372421de2bc38836702367f9 Kanban Board for Sprints (deprecated)]
 == 2 Week Sprint Meetings ==
-* 1st Sprint starts Monday, February 1st and will end Friday, February 12th
-* 2nd Sprint start Tuesday, February 16th and will end Friday, February 26th (Monday the 15th - US Holiday)
+{{Admin/note|Beginning in Q2 2016, we switched from two to three week (12 day) sprints. The new schedule is below.}}
-* 3rd Sprint starts Monday, February 29th and will end on Friday, March 11th
 {| class="wikitable"
@@ Line 32: / Line 58: @@
 ! Meeting !! Time and Days !! Attendees !! Notes
 |-
-| Sprint Planning Meeting || Every other Monday (first day of Sprints) || Core Team is required|| Stakeholders may listen in, This meeting lasts as long as it takes
+| Stand-up & Project Review || Mondays, 9-9:30 am PT. In-person (Eric Renaud's Vidyo room). || Core Team is required || Anyone is welcome to listen, but may not speak, take all questions offline to David and/or Eric.
+|-
+| Stand-up || Tuesdays and Thursdays, 9-9:15 am PT. In-person (Eric Renaud's Vidyo room). || Core Team is required || Anyone is welcome to listen, but may not speak, take all questions offline to David and/or Eric.
 |-
-| Daily Stand-Ups (15 minutes only) || 9:45am Pacific Everyday - Tuesday-Friday first week of Sprints, Monday-Friday second week of Sprints  || Core Team is required || Anyone is welcome to listen, but may not speak, take all questions offline to Mike or Jen
+| Team Time || Wednesdays, 9:15 - 10 am PT. In-person (Eric Renaud's Vidyo room). || Core Team is requested, Team only || No agenda, though the time slot may be leveraged for specific work, discussions or presentations.
 |-
-| Sprint Review Meeting || TBD Pacific every other Friday || Everyone is welcome || This is where we show the work completed in the sprint, it's a place to ask questions and give feedback
+| Sprint Demo Meeting || Every third Wednesday (last day of Sprint), time TBD|| Everyone is welcome || This is where we celebrate by showing the work completed in the sprint; it's a place to ask questions and give feedback. In Q2, all Durable Teams will started demoing to the full Marketing organization. In Q3, Functional Teams started showing their work in the Sprint Demo on a regular basis.
 |-
-| Sprint Retrospective Meeting || end of Sprint || Core Team Only || No One else is invited to this meeting
+| 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 Mike Alexis' Vidyo
+* All Meetings are in Eric Renaud's Vidyo
-* if you have questions about these meetings, please contact Mike
+* if you have questions about these meetings, please contact Eric
 == Team ==
-* Jennifer Bertsch (product owner)
+* Alex Gibson (Front-End Developer)
-* Mike Alexis (scrum master)
+* Craig Cook (Front-End Developer)
-* Holly Habstritt (UX designer)
+* David Tenser (Team Lead)
-* Michael Ham (designer)
+* Eric Renaud (Program Manager)
-* Troy Palmer (copywriter)
+* Jeffrey Taylor (Content Strategist)
-* Paul McLanahan (back-end dev)
+* Jennifer Rouse (UX designer)
-* Craig Cook (front-end dev)
+* Jon Petto (Front-End Developer)
-* Alex Gibson (front-end dev)
+* Mark Weaver (Designer)
-* Schalk Neethling (front-end dev)
+* Michael McCombie (Product Designer)
-* Jon Petto (front-end dev)
+* Raphael Raue (SEO)
+* Stephanie Hobson (Front-End Developer)
+* Vince Joy (UX/UI)