Engagement/MDN Durable Team/Processes: Difference between revisions

Engagement/MDN Durable Team/Processes (view source)

Revision as of 23:11, 7 June 2018

129 bytes added , 7 June 2018

→‎Planning Sprints: Updated based on using ZenHub instead of Taiga

Jswisher

canmove, Confirmed users

1,953

edits

@@ Line 50: / Line 50: @@
 ==Planning Sprints==
-Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Durable team members in the content, development, and community areas work separately to select and flesh out the User Stories in each area, so that they are ready to be placed in the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_Board|Task Board]]. The groups also review the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_|Tasks]] for each User Story, to ensure that they can be done in one Sprint, and are complete enough to ensure that the [[Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]] will be met.
+Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Durable team members in the content and development areas work separately to select and flesh out the User Stories in each area, so that they are ready to be placed in the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_Board|Task Board]]. The groups also review the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_|Tasks]] for each User Story, to ensure that they can be done in one Sprint, and are complete enough to ensure that the [[Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]] will be met.
-The whole team convenes for a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Planning_Meeting|Sprint Planning Meeting]] (usually on Thursday), to review and refine all the selected stories for the sprint. User stories are given "t-shirt" (S/M/L) size estimates, and confidence ratings (High/Medium/Low). The size estimate categories are based on the number of days they are expected to take to complete:
+The whole team convenes for a final [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Planning_Meeting|Sprint Planning Meeting]] (usually on Thursday), to review and refine all the selected stories for the sprint. User stories are given size estimates, and confidence ratings (High/Medium/Low). The size estimate categories are based on the number of "ideal" days they are expected to take to complete; ideal days would be those devoted to working on the story, without meetings, email, or other interruptions. Values can be from 1 to 5; stories that need more than 5 days should be broken into smaller stories.
-;Small
-: a few days
-;Medium
-: about a week
-;Large
-: more than a week, up to the whole sprint
-The team's committed User Stories are shared with the broader Marketing team.
 When prioritizing and planning a sprint, it is a good idea to consider "What will we want to demo at the end of the Sprint?" The user stories that are expected to lead to demo-worthy accomplishments should therefore get a high priority.
@@ Line 67: / Line 58: @@
 '''Tools'''
-* [https://tree.taiga.io/project/viya-mdn-durable-team/backlog Taiga backlog]
+* [https://github.com/mdn/sprints/labels#boards?repos=121649843,55001853,70901646,90252175,1352520,3311772,82040629,121278372,33677290,132630865,134759439&showPRs=false ZenHub user story board]
-* [https://docs.google.com/spreadsheets/d/1TTMsjNUKWg5H7EZh6U7DWhC_ZYzb6jwn4---JDnJyGI/edit?usp=sharing MDN 2016 Roadmap]
+* Story board for the Sprint; filter the main ZenHub board based on the milestone that represents the sprint.
-* Task board for the Sprint; each one has a unique URL within Taiga.[[#taskboard|*]]
-* [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board] in Taiga
 ===User Story Lifecycle===
-In addition to the Backlog, the MDN team uses the [https://tree.taiga.io/project/viya-mdn-durable-team/kanban Kanban board in Taiga] to track the status of User Stories in the planning process. The team represents the lifecycle of user stories with the following columns:
+The team represents the lifecycle of user stories with the following columns (a.k.a., "pipelines" in ZenHub parlance):
-; Draft
+; New Issues
-: The user story is proposed, but incomplete.
+: The user story is proposed, but has not been reviewed.
-; New
+; Epics
-: The author has added Acceptance Criteria and Tasks; it is ready for review by the team.
+: The user story is an epic with sub-stories; epics are usually not assigned to milestones.
-; Ready
+; Not Ready
-: The team accepts the user story as complete; it is ready to be prioritized and pushed into a sprint by the Product Owner. It '''must''' have acceptance criteria and tasks.
+: The story has been accepted to be worked on, but is missing components, such as [[/Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]], size estimates or confidence estimates. The missing pieces may be called out by the tags: NeedsAC, NeedsTimeEst, or NeedsConf.
+; Backlog
+: The team accepts the user story as complete; it is ready to be added into a sprint by assigning a milestone to it. It '''must''' have acceptance criteria, time estimates, and confidence estimates. Confidence estimates are made by team members based on their guess as to how likely the story is to be finished during the sprint.
 ; In Progress
-: The user story has been committed for a Sprint, and at least one task is the In Progress task state.
+: The user story has been committed for a Sprint, and work has started on it.
-; Ready for Test
+; Review/Test
-: All tasks have been completed; it is ready for review of the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]] by the Product Owner.
+: All tasks have been completed; it is ready for review by subject-matter experts (for content stories), or code review by a peer (for development stories).
 ; Done
-: The Acceptance Criteria and Definition of Done have been met.
+: The work and reviews have been completed. It is ready for sign-off by the Product Owner.
-; Archived
+; Closed
-: User stories that have been abandoned in Ready or In Progress with a comment explaining why they were abandoned (?? and those that were Done in a previous quarter ??).
+: The Product Owner has signed off, based on the Acceptance Criteria and [[Engagement/MDN_Durable_Team/Agile_glossary#Definition_of_Done|Definition of Done]], and has closed the issue.
+; Icebox
+: The issue is valid, but is not going to be worked on by the core staff team. It might be picked up by a volunteer. Or, the issue is deferred, but the future sprint it will go in is not defined.
 The following practices concern maintaining user story status:
-* User stories that are abandoned in the Draft or New states are deleted from Taiga.
+* If a user story is blocked in such a way that it can't be completed during a sprint, it should be removed from the sprint milestone (with an explanatory comment).
-* If a user story is blocked in such a way that it can't be completed during a sprint, it should be removed from the sprint back to the backlog (with an explanatory comment).
+* If a user story is in Done, 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 removed from a sprint back to the backlog, it should be moved back to the Ready state.
-* 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.
 ==Managing Work==