Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
student:vivifyscrum:help [2019/03/05 11:28] – bernstdhstudent:vivifyscrum:help [2019/03/05 11:30] – bernstdh
Line 61: Line 61:
   - 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).   - 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).   - 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}}. +  - Add a checklist to each feature (sprintable story) in the sprint backlog that contains the acceptance criteria. 
-  - Decompose each feature (sprintable story) in the sprint backlog into sub-items by clicking on {{student:vivifyscrum: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.+  - Decompose each feature (sprintable story) in the sprint backlog into subitems. Each subitem should correspond to a task. You can name tasks with phrases and they do not need to be user stories. You should mark subitems as tasks using the drop-down menu on the top left of the card that pops-up when you click on the sub-item.
   - Enter an effort estimate for each task. While it is a good idea to estimate stories in story points and tasks in hours, that isn't possible in 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.   - Enter an effort estimate for each task. While it is a good idea to estimate stories in story points and tasks in hours, that isn't possible in 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).   - 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).