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:help [2020/04/07 10:56] – bernstdhstudent:scrumj:help [2025/08/21 16:29] (current) – bernstdh
Line 1: Line 1:
- 
 ====User Interaction==== ====User Interaction====
  
 The user interface for scrumj looks something like the following: The user interface for scrumj looks something like the following:
  
-{{student:scrumj:ui.png}}+{{student:scrumj:ui.png|The scrumj User Interface}}
  
 Headings/labels are in **bold**, the headings/labels of cells that can't be edited are in //**italic bold**//, and the headings/labels that can/should only be changed using the <key>scrumj</key> menu are in __**underlined bold**__ Headings/labels are in **bold**, the headings/labels of cells that can't be edited are in //**italic bold**//, and the headings/labels that can/should only be changed using the <key>scrumj</key> menu are in __**underlined bold**__
Line 12: Line 11:
 ====Getting Started==== ====Getting Started====
  
-A sprint backlog can be created using the [[ https://docs.google.com/spreadsheets/d/1bI35ElgIrMCnwfhddW3lgvfDJKuZNDEJL4yiaKWd6ig/copy | scrumj link ]] (which actually makes a copy of an empty sprint backlog).+A sprint backlog can be created using the [[ https://docs.google.com/spreadsheets/d/1bI35ElgIrMCnwfhddW3lgvfDJKuZNDEJL4yiaKWd6ig/copy | scrumj link ]] (which actually makes a copy of an empty sprint backlog).  This document should then be shared with all members of the team (including the product owner).
  
-When a sprint backlog is initially copied it contains just an Overview page and an Assignments page. The first things a user should do after copying a sprint is to re-name it (in the usual way), set the start/end dates (by clicking on <key>scrumj</key>+<key>Set dates...</key>), and add **all** of the team members to the Assignments page by entering their names in the cells to the right of the header/label. (Note: You cannot add team members after you have added a story, so add all of them now.) +When a sprint backlog is initially copied it contains just an Overview page and an Assignments page. The first things a user should do after copying a sprint is to re-name it (in the usual way), set the start/end dates (by clicking on <key>scrumj</key>+<key>Set dates...</key>), and add **all** of the team members to the Assignments page by entering their names in the cells to the right of the header/label. (Notes: 1. The start date should be the date the sprint actually starts, not the date of the planning meeting. 2. You cannot add team members after you have added a story, so add all of them now.) 
  
-A story can be added to a sprint by clicking on <key>scrumj</key>+<key>Add one story</key> or <key>scrumj</key>+<key>Add multiple stories</key>. The tabs for the stories are color-coded as follows.+Note that the first time you use the scrumj menu you may be asked to give a script attached to the document permission to run. You must give the script (which is named ''%%scrumj.gs%%'') permission to do so. 
 + 
 +A story can be added to a sprint by clicking on <key>scrumj</key>+<key>Add one story</key> or <key>scrumj</key>+<key>Add multiple stories</key>. As with most names, it is better to avoid the use of spaces (which are normally used as delimiters) and special characters in story names. 
 + 
 +The tabs for the stories are color-coded as follows.
  
 ^ Color ^ Meaning ^ ^ Color ^ Meaning ^
-| <html><span style="color:#00CC00">Green</span></html> | All tasks completed and all acceptance criteria confirmed | +| <color green>Green</color> | All tasks completed and all acceptance criteria confirmed | 
-| <html><span style="color:#FFFF00">Yellow</span></html> | All tasks completed but some acceptance criteria unconfirmed | +| <color yellow>Yellow</color> | All tasks completed but some acceptance criteria unconfirmed | 
-| <html><span style="color:#FFA500">Orange</span></html> | Some tasks incomplete but, somehow, all acceptance criteria confirmed | +| <color orange>Orange</color> | Some tasks incomplete but, somehow, all acceptance criteria confirmed | 
-| <html><span style="color:#CC0000">Red</span></html> | Some tasks incomplete | +| <color red>Red</color> | Some tasks incomplete | 
-| <html><span style="color:#000000">Black</span></html> | Story was deactivated during sprint planning meeting |+| <color black>Black</color> | Story was deactivated during sprint planning meeting |
  
 The name of the active tab is rendered in green. The name of the active tab is rendered in green.
Line 32: Line 35:
 The Overview page provides an overview of the sprint and the progress that has been made thus far. It looks something like the following: The Overview page provides an overview of the sprint and the progress that has been made thus far. It looks something like the following:
  
-{{student:scrumj:overview-page.png}}+{{student:scrumj:overview-page.png|The Overview Page}}
  
  
Line 48: Line 51:
 The Assignments page provides a summary of the various work items that each team member has volunteered for. (The term "assignment" is a bit of a misnomer, given the way the Scrum process works.) **It is also where the names of the team members are entered.** It looks something like the following: The Assignments page provides a summary of the various work items that each team member has volunteered for. (The term "assignment" is a bit of a misnomer, given the way the Scrum process works.) **It is also where the names of the team members are entered.** It looks something like the following:
  
-{{student:scrumj:assignments-page.png}}+{{student:scrumj:assignments-page.png|The Assignments Page}}
  
 The task summary and acceptance criteria summary contain statistics about all of the stories in the sprint (except those that have been deactivated). It is presented for each team member individually. The task summary and acceptance criteria summary contain statistics about all of the stories in the sprint (except those that have been deactivated). It is presented for each team member individually.
Line 60: Line 63:
 A story page looks something like the following: A story page looks something like the following:
  
-{{student:scrumj:story-page.png}}+{{student:scrumj:story-page.png|The Story Page}}
  
 The story description can be entered "in as-I want-so" format by typing in the corresponding cells. The story description can be entered "in as-I want-so" format by typing in the corresponding cells.
Line 68: Line 71:
 A task or acceptance criteria will always be added at the end of the respective area and will be numbered accordingly. The user must enter the description and assignee (and effort for tasks). When a task is completed or an acceptance criteria is confirmed, the user should click on the corresponding status checkbox. The date will be entered automatically and, if permissions have been granted, the name of the person who clicked the status box will also be entered. A task or acceptance criteria will always be added at the end of the respective area and will be numbered accordingly. The user must enter the description and assignee (and effort for tasks). When a task is completed or an acceptance criteria is confirmed, the user should click on the corresponding status checkbox. The date will be entered automatically and, if permissions have been granted, the name of the person who clicked the status box will also be entered.
  
-The information in the effort+The information in the effort summary, task summary, and acceptance criteria summary is calculated from the information in the task area and acceptance criteria area. 
 ====User Interaction==== ====User Interaction====
- summary, task summary, and acceptance criteria summary is calculated from the information in the task area and acceptance criteria area. 
  
 A task can be removed by clicking on <key>scrumj</key>+<key>Delete one task...</key>. Similarly, an acceptance criterion can be removed by clicking on <key>scrumj</key>+<key>Delete one acceptance criterion...</key>. A task can be removed by clicking on <key>scrumj</key>+<key>Delete one task...</key>. Similarly, an acceptance criterion can be removed by clicking on <key>scrumj</key>+<key>Delete one acceptance criterion...</key>.