Gohelp software rota: Difference between revisions
No edit summary |
No edit summary |
||
Line 31: | Line 31: | ||
| Ben | | Ben | ||
| December 5th | | December 5th | ||
|- | |- | ||
| Mary | | Mary | ||
| December 12th | | December 12th | ||
| * | |||
|- | |- | ||
| Heiko | | Heiko |
Revision as of 13:06, 12 December 2011
Seth | October 3rd | |
Tony | October 10th | |
Chris | October 17th | |
Ben | October 24th | |
Mary | October 31st | |
Heiko | November 7th | |
Seth | November 14th | |
Tony | November 21st | |
Chris | November 28th | |
Ben | December 5th | |
Mary | December 12th | * |
Heiko | December 19th |
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.