Engagement/MDN Durable Team/Processes: Difference between revisions

Jump to navigation Jump to search

Engagement/MDN Durable Team/Processes (view source)

Revision as of 21:47, 23 April 2018

992 bytes removed ,  23 April 2018
Removed "Connecting epics and user stories" -- no longer relevant; other minor updates
(Removed Opportunity process to a separate page)
(Removed "Connecting epics and user stories" -- no longer relevant; other minor updates)
Line 4: Line 4:


==Assessing Product Opportunities==
==Assessing Product Opportunities==
The MDN team uses an [[/Engagement/MDN_Durable_Team/Processes/Opportunity_Assessment|Opportunity Assessment Process]] to evaluate, rank, and flesh out proposed significant changes to the MDN product.
The MDN team uses an [[Engagement/MDN_Durable_Team/Processes/Opportunity_Assessment|Opportunity Assessment Process]] to evaluate, rank, and flesh out proposed significant changes to the MDN product.
 
===Connecting Epics and User Stories===
 
An Epic is a task or project which is too large in scope to be completed in a single sprint (currently 12 business days), so it must be broken down into multiple User Stories.
 
As of October 2016, Taiga added built-in support for epics, so that user stories are linked with the epic they are associated with.
 
Previously the MDN team represented epics as a type of "issue". Epic issues are linked to their user stories, and the user stories are tagged with the issue ID of their epic (for example, "epic 211"). For the mechanics of doing this in Taiga, see [https://tree.taiga.io/project/viya-mdn-durable-team/wiki/connecting-epics-and-user-stories Connecting Epics and User Stories] in the Taiga wiki.
 
'''Tools'''
 
* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
* [https://tree.taiga.io/project/viya-mdn-durable-team/epics List of epics]
* [https://tree.taiga.io/project/viya-mdn-durable-team/issues?page=1&types=404887 Old list of Epics] (as issues, prior to built-in support for epics in Taiga)
 


==Prioritizing Work==
==Prioritizing Work==
Line 31: Line 16:
* IT infrastructure requirements and deadlines
* IT infrastructure requirements and deadlines


[[Engagement/MDN_Durable_Team#Objectives_and_Key_Results|Quarterly Key Results are listed on the MDN Durable Team's wiki page.]] Starting in Q2 2017, the team creates a Project document for each Key Result, linked from the wiki page. These documents summarize the purpose, success metrics, accountability matrix, and other key elements of the project.
[[Engagement/MDN_Durable_Team#Objectives_and_Key_Results|Quarterly Key Results are listed on the MDN Durable Team's wiki page.]] For many efforts, the team creates a Project document, linked from the wiki page. These documents summarize the purpose, success metrics, accountability matrix, and other key elements of the project.


'''Tools'''
'''Tools'''
Line 39: Line 24:


===Triaging Requests===
===Triaging Requests===
In addition to Epics and User Stories driven by organizational priorities as described above, requests for work to be done by the MDN durable team also arrive in the form of [https://bugzilla.mozilla.org/ Bugzilla] "bugs", in several forms:
In addition to [[Engagement/MDN_Durable_Team/Agile_glossary#Epic|Epics]] and [[Engagement/MDN_Durable_Team/Agile_glossary#User_Story|User Stories]] driven by organizational priorities as described above, requests for work to be done by the MDN durable team also arrive in the form of [https://bugzilla.mozilla.org/ Bugzilla] "bugs", in several forms:


* [https://mzl.la/DocRequests Requests for documentation changes] (product="Developer Documentation")
* [https://mzl.la/DocRequests Requests for documentation changes] (product="Developer Documentation")
* [https://mzl.la/DDN Mozilla product issues with the "dev-doc-needed" keyword set]
* [https://mzl.la/DDN Mozilla product issues with the "dev-doc-needed" keyword set]
* [https://mzl.la/MDNBugs Requests for changes to the MDN platform] (product="Mozilla Developer Network")
* [https://mzl.la/MDNBugs Requests for changes to the MDN platform] (product="developer.mozilla.org")


The process for triaging the first two types of requests is [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Processes/Documentation_bugs documented on MDN].  
The process for triaging the first two types of requests is [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Processes/Documentation_bugs documented on MDN].  
Line 104: Line 89:
* When all tasks are completed on a user story, it must be manually moved into Ready for Test by the owner of the user story.
* When all tasks are completed on a user story, it must be manually moved into Ready for Test by the owner of the user story.
* If a user story is in Ready for Test, but the product owner finds that the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]] are not complete, it should be moved back to In Progress, and more tasks added that will enable it to reach completion.
* If a user story is in Ready for Test, but the product owner finds that the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]] are not complete, it should be moved back to In Progress, and more tasks added that will enable it to reach completion.


==Managing Work==
==Managing Work==
Jswisher
canmove, Confirmed users
1,953

edits

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

Navigation menu