Engagement/MDN Durable Team/Agile glossary: Difference between revisions

← Older edit

Engagement/MDN Durable Team/Agile glossary (view source)

Revision as of 21:39, 21 June 2019

265 bytes removed , 21 June 2019

→‎Retrospective

Jswisher

canmove, Confirmed users

1,953

edits

@@ Line 17: / Line 17: @@
 ===Epic===
 A large-scale User Story that takes more than one Sprint to complete. An epic should be decomposed into User Stories that do fit within a Sprint.
-The MDN durable team uses [https://tree.taiga.io/project/viya-mdn-durable-team/issues?page=1 "issues" in Taiga] to represent epics, with tags based on the issue number to associate User Stories with their corresponding epic.
 ===Initiative===
@@ Line 30: / Line 28: @@
 [Role] A team member who executes Tasks, collaborates with the Product Owner on vision and priorities, and decides what work gets done and when. While all team members have specialized skills, in theory, any maker can take on any Task.
-===Mid-sprint check-in===
+===Mid-sprint review===
-[Meeting] This 15-minute meeting is a process check on how the sprint is going, adjustments that need to be made immediately, and progress toward completing committed user stories for the sprint. It is held near the middle of the sprint, usually the 6th or 7th work day.
+[Meeting] This brief meeting is a process check on how the sprint is going, adjustments that need to be made immediately, and progress toward completing committed user stories for the sprint. It is held near the middle of the sprint.
 ===Product Owner===
@@ Line 42: / Line 40: @@
 * What should we '''start''' doing?
 * What should we '''stop''' doing?
-* What should we '''continue''' doing?
+* What should we '''change''' how we're doing something?
 ===Scrum Master===
-[Role] A project manager who drives projects, manages the team's process, removes blockers, and facilitates meetings.
+[Role] A project manager who drives projects, manages the team's process, removes blockers, and facilitates meetings. Also called an "agile coach".
 ===Sprint===
-A set period of time designated to achieve a body of work. Currently, Mozilla Marketing teams use sprints on a 3-week schedule, with 12 days of sprint 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, the MDN team uses sprints on a 3-week schedule, with 12 days of sprint work time, and 3 days for review of the past sprint, planning of the next sprint, and miscellaneous non-sprint activity.
 ===Sprint Planning Meeting===
@@ Line 54: / Line 52: @@
 ===Sprint Review===
-[Meeting] Also called a "Sprint Demo", this meeting is a chance for teams to ''demonstrate completed work'' at the end of a Sprint. All Marketing Durable Teams share their work in a single review meeting, to share and celebrate everyone's work. Demos are informal, and slide presentations are discouraged. A team's demo need not cover all User Stories completed during a Sprint, but should highlight big achievements and wins.
+[Meeting] Also called a "Sprint Demo", this meeting is a chance for teams to ''demonstrate completed work'' at the end of a Sprint. All Marketing Durable Teams share their work in a single review meeting, to share and celebrate everyone's work. Demos are informal, and slide presentations are discouraged. A team's demo need not cover all User Stories completed during a Sprint, but should highlight significant achievements and big wins.
 ===Standup===
-[Meeting] A brief (15-minute) meeting that happens daily during the "work" days of a Sprint, in which team members discuss what they've done, what they plan to do, and anything blocking their work. Questions or discussions should be taken offline out of the meeting.
+[Meeting] Typically, this is a brief (15-minute) meeting that happens daily during the "work" days of a Sprint, in which team members discuss what they've done, what they plan to do, and anything blocking their work. Questions or discussions should be taken offline out of the meeting.
-* Team members are required to attend; if attendance is not possible, email the team with status.
-* Stakeholders are welcome to attend, but should primarily listen.
 ===Task===
@@ Line 68: / Line 63: @@
 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.
+The MDN durable team uses [https://app.zenhub.com ZenHub] for its task board; there is a browser extension that enables viewing the task board, and using related features, while working in the GitHub web UI.
 ===User Story===