Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan helpdesk at the competition #524

Closed
PeterJCLaw opened this issue Jan 18, 2020 · 4 comments
Closed

Plan helpdesk at the competition #524

PeterJCLaw opened this issue Jan 18, 2020 · 4 comments
Assignees
Labels
I: Should Have This task is relatively high priority, but we can survive without Won't Fix This will not be worked on

Comments

@PeterJCLaw
Copy link
Member

Helpdesk is the single-point-of-contact for teams to get help with their robots. We need to plan who will run this on the day as well as the various things it needs to be able to help the teams.

Original

comp/pits/helpdesk/main

Dependencies

@PeterJCLaw PeterJCLaw added the I: Should Have This task is relatively high priority, but we can survive without label Jan 18, 2020
@PeterJCLaw PeterJCLaw added this to the SR2020 Competition milestone Jan 18, 2020
@TomWheal
Copy link
Member

Happy to take this on, as I can now confirm i can attend the compeition

@PeterJCLaw
Copy link
Member Author

Moving conversation from #119 (Kit Team/Competition Team discussion about how to run helpdesk):

@RealOrangeOne wrote srobo/competition-team-minutes#199 (comment):

I had a chat with @TomWheal this evening, the outcome was:

  • Those assigned to helpdesk should have a working knowledge of the kit, and how to use it.
  • "Team Kits" label is fine for separating issues, but as always, if someone sees an issue and can help, they can / should. It's not the competition team's task list!
  • Those assigned to helpdesk should not be the ones handing out batteries, there should be a (perhaps physical) divide
  • Tom, if available, will take the "Head Helpdesk" role. Remaining committee / team members should be scheduled as usual, however a skew towards kit-related roles is probably ideal.

@PeterJCLaw wrote srobo/competition-team-minutes#199 (comment):

Thanks, that mostly sounds good.

  • Those assigned to helpdesk should not be the ones handing out batteries, there should be a (perhaps physical) divide

I'm surprised and a little concerned about this. What's the rationale for this?

It strikes me that this is going to mean that a lot of requests for batteries will get the response "I can't help with that, go over there (pointing along the desk)" as well as mean that two volunteers are now needed to permanently sit at Helpdesk where previously only a single one was needed. Moreover the person sat handing out batteries will have very little to do but be unable to actually help teams.

Previously we have had a pot of batteries at Helpdesk and allowed any volunteer there to hand them out. I'm not aware that there have ever been issues with this.

@TomWheal wrote srobo/competition-team-minutes#199 (comment):

I'm surprised and a little concerned about this. What's the rationale for this?

There were times last year where there was such a big queue for batteries it was causing a firerisk, becasue all the volenteers were busy handling technical problems with teams. Moving the technical help of the help desk will help with this as well, so its likley batteries will still be available on the help desk.

Ah, right. That's definitely undesirable -- both that we had queues and that they became problematic in themselves.

When helpdesk was first thought up, the original intent was that helpdesk was primarily a triage point, rather than being the place which actually solved the competitors' problems.
With that in mind, the protocol (a long time ago) was something like:

  1. competitor briefly outlines their problem
  2. if there's a known solution the competitor is told about it, otherwise
  3. helpdesk records this and tells the competitor that someone will come to help them
  4. when a volunteer is next free, they pick the next issue from the list

This should mean that helpdesk itself is low-latency and high throughput, with low chance of queueing. It also means that robot analysis (etc.) all happens in pits rather than at helpdesk, so the desk itself doesn't need a lot of space.

Aside: note that the above protocol also means we get a list after the competition of all the known issues and their solutions, which was intended to help us improve the kits. I'm not sure how much we actually used that information nor how useful it was though.

I've a feeling that at Newbury we were spoilt for space and so ended up doing a bunch of diagnostics at helpdesk itself, which was probably fine there, but works less well in a smaller venue.

Perhaps something closer to the original protocol could be considered?

@TomWheal
Copy link
Member

That sounds like a reasonable idea, currently my idea was to have a seperate unadvertised desk where technical issues are dealt with. But what your suggesting could also work, Ill address this properly when I start the plan for the helpdesk

@PeterJCLaw
Copy link
Member Author

This is redundant in light of the lack of venue. We'll still be doing mentoring, however it will happen naturally via the forums.

@PeterJCLaw PeterJCLaw added the Won't Fix This will not be worked on label Jun 28, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: Should Have This task is relatively high priority, but we can survive without Won't Fix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants