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:scrumj:practices [2019/11/22 12:10] – bernstdhstudent:scrumj:practices [2022/04/22 16:05] (current) – bernstdh
Line 11: Line 11:
   * Every task should have a description, effort (in hours), and assignee.   * Every task should have a description, effort (in hours), and assignee.
   * Every acceptance criterion (also known as a definition of done) should have a description and assignee.   * Every acceptance criterion (also known as a definition of done) should have a description and assignee.
-  * The team member that is the assignee on a task should mark it as "Checked" when it is completed. +  * The team member that is the assignee on a task should "check" its status checkbox when it is completed. 
-  * The team member that is the assignee on an acceptance criterion task should mark it as "Checked" when it is confirmed.+  * The team member that is the assignee on an acceptance criterion task should "check" its status checkbox when it is confirmed.
  
 ==== Practices for Creating Sprint Backlogs ==== ==== Practices for Creating Sprint Backlogs ====
Line 26: Line 26:
 1. Click on the [[ https://docs.google.com/spreadsheets/d/1bI35ElgIrMCnwfhddW3lgvfDJKuZNDEJL4yiaKWd6ig/copy | scrumj link ]] to create a copy of a blank document. 1. Click on the [[ https://docs.google.com/spreadsheets/d/1bI35ElgIrMCnwfhddW3lgvfDJKuZNDEJL4yiaKWd6ig/copy | scrumj link ]] to create a copy of a blank document.
  
-2. Rename the copy to "Sprint1". (Note: It is a good idea to avoid the use of spaces.)+2. Rename the copy to something appropriate or to the name you were told to use. (Note: It is a good idea to avoid the use of spaces in identifiers of all kinds since they are often used as delimiters.)
  
-3. Add the team members to the "Assignments" page using just their eids.+3. Set the start/end dates by clicking on <key>scrumj</key>+<key>Set dates...</key>. (Note: The start date should be the date the sprint actually starts, not the date of the planning meeting.)
  
-4. Share the copy with all other team members and the product owner using their eid@dukes.jmu.edu account.+4. Add **all** of the team members to the "Assignments" page using just the ''local-part'' (i.e., the part before the ''@'' sign) of each member's email address (at JMU, this is the person's eid). NOTE: You cannot add team members after a story has been added. So, you must add all team members now. 
 + 
 +5. Share the copy with all other team members using their eid@dukes.jmu.edu account and with the product owner using her/his eid@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</key>+<key>Update Assignments</key>.+11. Click on <key>scrumj</key>+<key>Update Assignments</key>.
  
 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:
  
-11. Click on "Deactivated?"+12. Click on "Deactivated?"
  
-12. Click on <key>Scrum</key>+<key>Update Assignments</key>.+13. Click on <key>scrumj</key>+<key>Update Assignments</key>.
  
-Alternatively, you could delete. However, you will then lose all of the information you entered about them.+Alternatively, you could delete the story. However, you will then lose all of the information you entered about them.
  
 After you have finalized the sprint backlog, remember to: After you have finalized the sprint backlog, remember to:
  
-13. Delete the stories from the product backlog.+14. Delete the stories from the product backlog.
  
  
Line 69: Line 71:
 1. Copy the document containing the backlog for Sprint N-1. 1. Copy the document containing the backlog for Sprint N-1.
  
-2. Rename the copy to "SprintN" (with N replaced by the appropriate number).+2. Rename the copy to "sprintNteamXX" (with N replaced by the appropriate number and XX replaced by your team number).
  
 3. Click on <key>Scrum</key>+<key>Delete completed stories</key>. 3. Click on <key>Scrum</key>+<key>Delete completed stories</key>.
  
-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 <key>scrumj</key>+<key>Set dates...</key>. (Note: The start date should be the date the sprint actually starts, not the date of the planning meeting.) 
 + 
 +5. Share the copy with all other team members using their eid@dukes.jmu.edu account and with the product owner using her/his eid@jmu.edu account.
  
-5.-13. Use the process for Sprint 1+6.-14. Use the process for Sprint 1
  
 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).