Webmaker/Events: Difference between revisions

Jump to navigation Jump to search

Webmaker/Events (view source)

Revision as of 14:32, 22 April 2014

5,857 bytes removed ,  22 April 2014
Replaced content with "__NOTOC__ https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png =What we're shipping in Q2= ===Key links=== <onlyinclude> <bugzilla> { "product": "webma..."
(Created page with "__NOTOC__ https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png =What we're shipping in Q2:= ** 1) '''DEFINITIONS''' -- '''Document the on-ramps'''. As user stori...")
 
(Replaced content with "__NOTOC__ https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png =What we're shipping in Q2= ===Key links=== <onlyinclude> <bugzilla> { "product": "webma...")
Line 1: Line 1:
__NOTOC__
__NOTOC__
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ry8lxg84.png
=What we're shipping in Q2:=
=What we're shipping in Q2=
** 1) '''DEFINITIONS''' -- '''Document the on-ramps'''. As user stories. "When users do x, we want to count and respond like y."
** 2) '''INFRASTRUCTURE''' -- '''Wire the on-ramps.''' So we can a) count and b) respond when people walk through them.
** 3) '''COMMUNICATIONS''' -- '''Communicate to the on-rampees.''' The messages users receive once they walk through. With the right calls to action to do more.
** 4) '''NEW: USABILITY TESTING''' -- '''User test the on-ramps.''' Where are these users getting stuck or stubbing their toe on these on-ramps? Clear away these blockers to increase our conversion rates.


===Key links===
* '''[https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=0 DEFINITIONS SPREADSHEET]''' -- http://mzl.la/contribution_pathways -- Contribution Pathways. User stories that list the counting and responses we need. Broken down by sprint'''
* '''[http://adamlofting.github.io/mofo-contributors-dashboard/ CONTRIBUTION DASHBOARD] (prototype)''' -- Pulling in and visualizing contributor data
* [https://wiki.mozilla.org/Webmaker/Contribution ENGAGEMENT LADDER]. High level. Our user, supporter, contributor funnel. How Webmaker contributors TEACH, BUILD and ORGANIZE.


https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/8riscpl0.png


=1) DEFINITIONS =
===Key links===
===DEFINITIONS v2 (April 2) (COMPLETE)===
* '''Goal''': MVP user stories. Covering the key bases: signing up, entering an event, etc. ([https://docs.google.com/spreadsheet/ccc?key=0Al0Wg7eR7tHcdGxNNE41RTl4eHBLNG92ZXBHY2l6MkE&usp=sharing#gid=6 COMPLETED HERE])
* '''Roles''': R: '''Michelle''' A: '''Claw''' C: '''Amira, Jbuck, Andrea''' I: webmaker-dev, mozteach
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[definitions-v2]'''
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
===DEFINITIONS v3 & v4 (April 9) (COMPLETE)===
* '''Goal''': From user to contributor. Additional use cases beyond the MVP: signing up for training, presenting on a community call, etc.
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[definitions-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>


=2) Infrastructure=
=== INFRASTRUCTURE v1 (April 11)===
* '''Goal''': Trigger counting and communications for MVP users stories cases documented in the "definitions" sprint.
* '''Roles''':  R:  '''Jbuck''' A: '''Brett''' C: '''Adam, Michelle, Andrea''' I: '''mozteach, webmaker-dev, engagement team'''
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev1'''
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev1",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
=== INFRASTRUCTURE v2 (April 25 -- before All Hands?)===
* '''Goal''': Trigger counting and response for the V3 users stories cases documented here: http://mzl.la/contribution_pathways
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''infrastructurev2'''
* '''File one of these tickets''': http://mzl.la/infrastructurev2
<onlyinclude>
<bugzilla>
{
"product": "Webmaker",
"status_whiteboard": "infrastructurev2",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>


= 3) Communications =
=== COMMUNICATIONS v2 (April 15)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': 1) Review and write current and new email responses. For sign-up, events, teaching kits and remix.
* 2) Learn and model best practices. Learn how to get good at this.
** (Use this for best practices: http://reallygoodemails.com/ and CC Andrea on all tickets)


===Key links===
* '''Email copy''': current drafts for all email responses is here: https://teach.etherpad.mozilla.org/emailengagementtemplates
* '''Bugzilla''': Component: '''Engagement Ladder''' | Whiteboard tag: '''[communications-v2]''' | [http://mzl.la/1dNhNox File one of these tickets]
<onlyinclude>
<onlyinclude>
<bugzilla>
<bugzilla>
{
{
"product": "webmaker",
"product": "webmaker",
"component":"Engagement Ladder",
"component":"Events",
"whiteboard": "[communications-v2]",
"whiteboard": "foo",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"maxrows":"50",
Line 100: Line 21:
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
=== COMMUNICATIONS v3 (April 25 -- before All Hands)===
* '''Roles''': R: '''Lainie''' A: '''Brett & Matt''' C: '''Amira, Jbuck, ErikaD, Andrea'''
* '''Goal''': Write the emails. Plus optimization and housekeeping from v2.
<onlyinclude>
<bugzilla>
{
"product": "webmaker",
"component":"Engagement Ladder",
"whiteboard": "[communications-v3]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>
</onlyinclude>
= 4) USABILITY TESTING v1 (April 25)=
* Do initial user testing for the V2 and V3 user stories listed here: http://mzl.la/contribution_pathways
* Where are users getting stuck? What are quick wins for addressing them?
* Blog, triage key learnings together, and then file those learnings as actionable tickets.
Tickets to file:
** Sign-up: do usability testing and document key learnings
** Event creation: do usability testing and document key learnings
** Submit a teaching kit
Lower priority:
** Sign up and on-boarding for Webmaker training (???)
** Attend and present in a Webmaker community call (???)
** Translation and localization (???)
** Participate in Webmaker QA or testing (???)
===Quick Links===
'''Engagement Ladder tickets'''
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Webmaker&component=Engagement%20Ladder File a ticket]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=9811999&query_format=advanced&component=Engagement%20Ladder&product=Webmaker See all tickets]
Matt Thompson
Confirmed users
9,624

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/967445"

Navigation menu