| Next revision | Previous revision |
| student:scrumj:help [2019/11/22 16:02] – created bernstdh | student:scrumj:help [2023/06/26 11:09] (current) – [Getting Started] Remove embedded HTML lam2mo |
|---|
| {{student:scrumj:ui.png}} | {{student:scrumj:ui.png}} |
| |
| Headings/labels are in **bold**. The headings/labels of cells that can't be edited are also **//italic//**. | 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**__ |
| |
| In general, you should not use the "standard" spreadsheet commands to add/delete rows/columns/sheets. Instead, you should use the <key>scrumj</key> menu. Menu items that end in ellipses (i.e., ...) will prompt you for additional information. | In general, you should not use the "standard" spreadsheet commands to add/delete rows/columns/sheets. Instead, you should use the <key>scrumj</key> menu. (Menu items that end in ellipses (i.e., ...) will prompt you for additional information.) Each tab is protected to help prevent you from making changes to cells that should only be changed from the <key>scrumj</key>. However, you can, if you think it is necessary, remove the protections using the "standard" spreadsheet commands (i.e., click on <key>Data</key>+<key>Protected sheets and ranges</key>). You can also reset the protections for stories by clicking on <key>scrumj</key>+<key>Fix protections on current story</key>. |
| |
| ====Getting Started==== | ====Getting Started==== |
| |
| A sprint backlog can be created/copied using the [[ https://docs.google.com/spreadsheets/d/1bI35ElgIrMCnwfhddW3lgvfDJKuZNDEJL4yiaKWd6ig/copy | scrumj link ]]. | 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 the team members to the Assignments page (by entering their names in the cells to the right of the header/label). | 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">OrangeGreen</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. |
| |
| 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. | 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==== |
| |
| 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>. |
| |
| The current story can be deleted by clicking on <key>scrumj</key>+<key>Delete current story</key>. | The current story can be deleted by clicking on <key>scrumj</key>+<key>Delete current story</key>. |
| | |
| | |
| | ====Known Issues==== |
| | |
| | Because of a defect in Google Sheets, you will sometimes get an error message when you try to make a change to a story. This is because each sheet is protected (to prevent you from editing cells that you shouldn't), and the defect causes the protected ranges to be changed when they shouldn't be. The problems this causes can usually be corrected by clicking on <key>scrumj</key>+<key>Fix protections on current stories</key>. If this doesn't work, you can remove all protections (but you must then be careful not to change cells that you shouldn't change). |
| | |
