Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| student:scrumj:practices [2019/11/22 12:10] – bernstdh | student:scrumj:practices [2019/11/22 14:55] – Added the "Set dates..." step bernstdh | ||
|---|---|---|---|
| Line 28: | Line 28: | ||
| 2. Rename the copy to " | 2. Rename the copy to " | ||
| - | 3. Add the team members to the " | + | 3. Set the start/end dates by clicking on < |
| - | 4. Share the copy with all other team members and the product owner using their eid@dukes.jmu.edu account. | + | 4. Add the team members to the " |
| + | |||
| + | 5. Share the copy with all other team members and the product owner using their eid@dukes.jmu.edu account. | ||
| After the planning meeting begins, one team member should then: | After the planning meeting begins, one team member should then: | ||
| - | 5. Add all of the stories that the team expects to include in the sprint backlog. (In principle, this can be done by multiple players simultaneously but it is difficult to not create editing conflicts.) | + | 6. Add all of the stories that the team expects to include in the sprint backlog. (In principle, this can be done by multiple players simultaneously but it is difficult to not create editing conflicts.) |
| Then, multiple team members can simultaneously add details to each story: | Then, multiple team members can simultaneously add details to each story: | ||
| - | 6. Copy the description of the story from the product backlog. | + | 7. Copy the description of the story from the product backlog. |
| - | 7. Enter the number of story points. | + | 8. Enter the number of story points. |
| - | 8. Add the tasks. | + | 9. Add the tasks. |
| - | 9. Add the acceptance criteria. | + | 10. Add the acceptance criteria. |
| After the details of all of the stories have been entered, one team member should: | After the details of all of the stories have been entered, one team member should: | ||
| - | 10. Click on <key>Scrum</ | + | 11. Click on <key>scrumj</ |
| If the team then decides to exclude some stories from the sprint, the best thing to do is: | If the team then decides to exclude some stories from the sprint, the best thing to do is: | ||
| Line 54: | Line 56: | ||
| 11. Click on " | 11. Click on " | ||
| - | 12. Click on <key>Scrum</ | + | 12. Click on <key>scrumj</ |
| Alternatively, | Alternatively, | ||
| Line 73: | Line 75: | ||
| 3. Click on < | 3. Click on < | ||
| - | 4. Share the copy with all other team members and the product owner using their eid@dukes.jmu.edu account. | + | 4. Set the start/end dates by clicking on < |
| + | |||
| + | 5. Share the copy with all other team members and the product owner using their eid@dukes.jmu.edu account. | ||
| - | Use the process for Sprint 1, starting with step 5. | + | 6.-14. |
| If Sprint N-1 does not contain either open stories or deactivated stories, the best thing to do is use the process for Sprint 1 (but using the appropriate sprint number). | If Sprint N-1 does not contain either open stories or deactivated stories, the best thing to do is use the process for Sprint 1 (but using the appropriate sprint number). | ||