Open adonahue opened 5 years ago
Todo: Research Automation / cheap labour tradeoffs.
Then more things...
@jaedoucette - how are we handling the time you allocate to this? Do we need to put an estimate on it?
@adonahue I'm thinking this is really more of an epic, rather than a single story. I can make cards as I start to work on the different elements perhaps? The breakdown might be:
[] Research Automation or cheap labour options (2 points) [] Find a suitable queuing / meeting room provider. (2 points) [] Make surveys in Qualtrix (3 points) [] Figure out Qualtrix calendar feature (1 point) [] Make an MTurk HIT for recruitment (2 points) [] Implement the document display feature for Riff (??? points / Dev work?) [] Recruit any needed operators and train them (2 points) [] Design test plan (1 point) [] Test entire system end-to-end with 8 people. (2 points)
@jaedoucette - that makes sense to me. I also think it makes sense to track them on the board since it will be a substantial amount of your time.
Since, as the PI, @ebporter is going to handle the oversight of the experiment, I think it makes sense for the two of you to more or less manage the cards for this epic. I want to understand it to the extent that I know how much of your capacity is left over for other work, but beyond that, I see it as a separate line of work from the product software development. Does that approach work for you and @ebporter ?
Yes, makes sense to me.
On Mon, Jul 15, 2019 at 1:49 PM Amy Donahue notifications@github.com wrote:
@jaedoucette https://github.com/jaedoucette - that makes sense to me. I also think it makes sense to track them on the board since it will be a substantial amount of your time.
Since, as the PI, @ebporter https://github.com/ebporter is going to handle the oversight of the experiment, I think it makes sense for the two of you to more or less manage the cards for this epic. I want to understand it to the extent that I know how much of your capacity is left over for other work, but beyond that, I see it as a separate line of work from the product software development. Does that approach work for you and @ebporter https://github.com/ebporter ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rifflearning/zenhub/issues/39?email_source=notifications&email_token=AB3RWLFQ3LSUN2KNPCLPJK3P7S2CVA5CNFSM4HODUZQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ6OS3I#issuecomment-511502701, or mute the thread https://github.com/notifications/unsubscribe-auth/AB3RWLACMNXFX7SLO3SZMFDP7S2CVANCNFSM4HODUZQQ .
This card is to track related to implementing the experiment. It probably should be an epic.
A plan for the the nest steps for implementation is here: https://docs.google.com/document/d/1wRdnZt13mSzFfYAJjmlPCdbVQJu3rdZOjKJXb-Ioqhc/edit
And the more detailed description of the experiment content and methodology is here: https://docs.google.com/document/d/1NjwE9ChCGNzXA1KqNq_jseWDS5fDvrOW9491DTgo8CI/edit
[] Research Automation or cheap labour options (2 points) [] IRB Proposal (5 points) [] Find a suitable queuing / meeting room provider. (2 points) [] Make surveys in Qualtrix (3 points) [] Figure out Qualtrix calendar feature (1 point) [] Make an MTurk HIT for recruitment (1 points) [] Implement the document display feature for Riff (??? points / Dev work?) [] Recruit any needed operators and train them (2 points) [] Design test plan (1 point) [] Test entire system end-to-end with 8 people. (2 points)