Gohelp software rota: Difference between revisions
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
| Seth | | Seth | ||
| June 11th | | June 11th | ||
| | | | ||
|- | |- | ||
| Tony | | Tony | ||
| June 18th | | June 18th | ||
| | | * | ||
|- | |- | ||
| Chris | | Chris | ||
Revision as of 14:12, 18 June 2012
| Seth | April 30th | |
| Tony | May 7th | |
| Chris | May 14th | |
| Ben | May 21st | |
| Mary | May 28th | |
| Heiko | June 4th | |
| Seth | June 11th | |
| Tony | June 18th | * |
| Chris | June 25th | |
| Ben | July 2nd | |
| Mary | July 9th | |
| Heiko | July 16th |
Purpose
To make sure that all email forwarded to the software group from GO Help is answered in a timely manner.
People in rota
Seth, Tony, Chris, Ben, Mary, Heiko
Process
We are going to use a rota where each person will be 'on duty' for 1 week at a time. Any questions hitting the software list during that time should be shepherded by the person on duty.
It is responsibility of the person on duty to make sure that all queries are answered by answering it themselves, forwarding it on to someone else who knows more, or harassing the software list until something happens. The person on duty must also make sure that any answer gets back to either the GO Help list or the originator of the query from GO Help.
At the end of your shift, please send a reminder email to the next person on the list to remind them that it's their turn.