Gohelp software rota: Difference between revisions
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
| Chris | | Chris | ||
| February 20th | | February 20th | ||
|- | |- | ||
| Ben | | Ben | ||
| February 27th | | February 27th | ||
| * | |||
|- | |- | ||
| Mary | | Mary | ||
Revision as of 12:52, 27 February 2012
| Heiko | December 19th | |
| Seth | December 26th | |
| Tony | January 2nd | |
| Chris | January 9th | |
| Ben | January 16th | |
| Mary | January 23rd | |
| Heiko | January 30th | |
| Seth | February 6th | |
| Tony | February 13th | |
| Chris | February 20th | |
| Ben | February 27th | * |
| Mary | March 5th | |
| Heiko | March 12th |
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.