Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
student:vivifyscrum:practices [2019/03/05 10:45] – bernstdhstudent:vivifyscrum:practices [2019/03/05 11:45] (current) – bernstdh
Line 1: Line 1:
-===== Help Using the Scrum Board in VivifyScrum =====+===== Vivify Scrum Practices and Conventions =====
  
-This page contains information about how to use the Scrum board in VivifyScru,.+Vivify Scrum uses some non-standard terminology (e.g., it does not use the term "acceptance criteria" or "definition of done" but does have "checklists") and allows some non-standard practices (e.g., tasks can have checklists). To use standard practices and avoid any confusion, you must use the following practices and comply with the following conventions.
  
 +  - Each sprintable backlog item must be have an item type of "Story".
 +  - Every sprintable backlog item must have a single checklist containing the  acceptance criteria.
 +  - Most sprintable backlog items should have subitems.
 +  - Every subitem must have an item type of "Task".
 +  - A task must not have a checklist. (A task should be small so a checklist would not provide any additional useful information.)
 +  - The team must have an assignee for every task.
 +  - Stories must not have assignees (since the individual tasks do).
 +  - The team member that is the assignee on a task must mark it as "Done" when it is completed.
 +  - The team must have (at least) one reviewer for every story.
 +  - Tasks must not have reviewers (because they will be reviewed by the reviewer for the story).
 +  - Epics can (and should) be included in the product backlog. Since there is no specific item type for epics, they must be classified as "Story".
 +  - Since VivifyScrum does not allow multiple levels of drill-down, when an  epic is decomposed into sprintable stories it must be removed from the product backlog.
  
-==== Working with the Product Backlog ==== +Help is available on the [[student:vivifyscrum:help | using VivifyScrum page ]].
- +
- +
-The product backlog will typically be the left-most column of the board and will be labeled "Backlog". +
- +
-     +
- +
-=== Adding a Product Backlog Item === +
- +
-To add a product backlog item (PBI): +
- +
-  - Hover the mouse over the bottom of the "Backlog" title bar until a <key>+</key> appears. +
-  - Click on the <key>+</key>. +
-  - Enter a title for the item. +
-  - Click on <key>SAVE</key>. +
-       +
- +
-==== Sprint Planning ==== +
- +
-Sprint Planning involves the following steps. +
-  - On the right side of the board (midway down the board), click on <key>+</key> (and name it Sprint #, where # is replaced by the appropriate number). +
-  - Chose which PBIs you want to do in this sprint and drag them from the PBI column to the Sprint # column (i.e., to the sprint backlog). +
-  - Make sure that each feature in the sprint backlog has completion criteria (called a checklist). Add them by clicking on {{student:vivifyscrum:vivifyscrum_checklist.png}}. +
-  - Decompose each feature (sprintable story) in the sprint backlog into sub-items by clicking on {{vivifyscrum_subitem.png}}. Each sub-item should correspond to a task. You can name tasks with phrases and they do not need to be user stories. You should mark sub-items as tasks using the drop-down menu on the top left of the card that pops-up when you click on the sub-item. +
-  - Make an estimate for each task by clicking on the "Points" drop-down on the right side of the card. (It is a good idea to estimate stories in story points and tasks in hours, but we can't do that with Vivify Scrum, so you will have to use story points for task estimates as well.) Note that when you associate items with sub-items, the parent item shows how many story points there are in the sub-items along with the estimate for the item. When you make all the sub-items for an item, these numbers should match. If they  don't. then change the item or sub-item estimates until they do. The idea is to use the tasks, which are smaller and hence easier to estimate, to improve your estimates for features and so to ensure that you have a reasonable collection of items in the sprint backlog. +
-  - Add items, such as overhead items, to the sprint backlog.  Pay specific attention to overhead items that are not associated with a particular PBI (e.g., grooming the product backlog). +
-  - Have team members take responsibility for tasks (and record the information in the tasks by editing the "assignees"). +
-  - When the team is happy with the stories and tasks in the sprint backlog, click on the menu drop-down to the right of the sprint name and choose <key>Start Sprint</key>. Note: Make sure the dates are correct. This will add a <key>Sprint Backlog</key> item to the left-side menu (that can be used to go to the task board). +
-       +
-It is often useful to filter both the product backlog and the sprint backlog +
-while planning. You can filter based on assignee, type, priority, etc... +
-using the {{vivifyscrum_filter.png}} button. +
-   +
- +
-==== Sprinting ==== +
- +
-As the sprint progresses, each team member should move their assigned tasks through the task board as they go. If a team member decides to work on an unassigned task, he or she should assign themselves to it - must be no tasks in the in-progress or done columns of the task board that do not have someone assigned to them. +
- +
-   +
-When a feature is complete, a reviewer should go through its checklist and make sure that all the completion criteria are satisfied (this could be part of some other task or a task on its own). +
-   +
- +
-==== Deleting a Board ==== +
- +
-Only the Owner can delete a board. To do so, first Archive it. Then, on "My Boards", click on <key>Delete</key>. +
-  +