canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes: Difference between revisions
Jump to navigation
Jump to search
Engagement/MDN Durable Team/Processes (view source)
Revision as of 20:59, 4 November 2016
, 4 November 2016→Connecting Epics and User Stories: updated for built-in support for epics
(→Proposing Work: update for epic support in Taiga) |
(→Connecting Epics and User Stories: updated for built-in support for epics) |
||
| Line 16: | Line 16: | ||
===Connecting Epics and User Stories=== | ===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. Taiga | |||
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. | |||
==Prioritizing Work== | ==Prioritizing Work== | ||