Qualifications
- S/he can complete a task assigned in an iteration.
- This requires that s/he can detect a problem of a task during the work if it exists and s/he can immediately report the problem in a reasonable format to the authors.
- This also requires that s/he can foresee potential issues in a new task and estimate the workload to judge whether s/he can complete it, when authors discuss the plan for next iteration in a weekly meeting.
- Thus, that s/he can complete a task in an iteration means that s/he can estimate the workload s/he can finish in an iteration and can complete the task once agreed if there is no unexpected problem and can detect and report a problem if it happened.
- S/he should be able to cleanly and efficiently organize the code and data files.
- A task is a set of the goal and general instruction to reach the goal. Thus, an assistant is not necessarily required to come up with the best way to reach the goal. However, it is of course better if s/he can suggest a better way to complete the task. In this case, an assistant should first consult the authors and work in it only give an approval.
Disqualified research assistants
- An assistant who regularly fails to complete a task simply because s/he underestimated the workload of the task is disqualified.
- An assistant who regularly fails to detect a problem is disqualified.
- An assistant who regularly fails to report a problem is disqualified.
- An assistant who regularly misunderstand either the goal or the instruction is disqualified.
- An assistant who never learn the coding rule and other policies and messes up the code and data files is disqualified.