canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Agile glossary: Difference between revisions
Engagement/MDN Durable Team/Agile glossary (view source)
Revision as of 14:58, 29 June 2016
, 29 June 2016Sprint board >> Task board
No edit summary |
(Sprint board >> Task board) |
||
| Line 35: | Line 35: | ||
===Sprint=== | ===Sprint=== | ||
A set period of time designated to achieve a body of work. Currently, Mozilla Marketing teams use 3-week sprints, which consist of 12 days of active work time, and 3 days for review of the past sprint, planning of the next sprint, and miscellaneous non-sprint activity. | A set period of time designated to achieve a body of work. Currently, Mozilla Marketing teams use 3-week sprints, which consist of 12 days of active work time, and 3 days for review of the past sprint, planning of the next sprint, and miscellaneous non-sprint activity. | ||
===Stand-up=== | ===Stand-up=== | ||
| Line 44: | Line 41: | ||
===Task=== | ===Task=== | ||
A chunk of work needed to deliver the Acceptance Criteria of a User Story. Tasks should be defined to take about a day to complete. Tasks that require more than a day or so may need to be divided into smaller tasks. | A chunk of work needed to deliver the Acceptance Criteria of a User Story. Tasks should be defined to take about a day to complete. Tasks that require more than a day or so may need to be divided into smaller tasks. | ||
===Task Board=== | |||
A visual representation of the team's work plan and status for a Sprint. Also called a Sprint Board. | |||
The MDN durable team uses [https://tree.taiga.io/project/viya-mdn-durable-team/ Taiga] for its task board. | |||
===User Story=== | ===User Story=== | ||