Updated: this CSV file has information on who taught when. The three columns are the person's unique identifier, the date on which they first qualified, and the dates on which they taught. (If someone has taught multiple times, there is one record for each teaching event.) People who haven't taught at all are at the bottom with empty values in the third column. Erin Becker's analysis of this data is posted on the Data Carpentry blog and discussed here.
We rebooted instructor training in October 2015, and things have been going pretty well since then. If we average over all 23 new-style classes, it looks like two thirds of people who take part actually qualify as instructors within four months of finishing the class:
|Date||Site(s)||Days Since||Participants||Completed||Percentage||Cum. Participants||Cum. Completed||Cum. %age|
|2016-04-17||North West U||31||23||0||0.0%||356||152||42.7%|
One of our goals for this year is to lower the majority completion time from four months to three; another is to increase the throughput from two thirds to three quarters. What I'd really like, though, is some help figuring out what statistical model to use for the other important aspect of our training and mentoring: how many of the people we train go on to actually teach workshops, and how quickly.
The data we have includes the following for each person:
- unique personal identifier (we can easy anonymize individuals)
- date(s) of the instructor training courses they took (someone may enroll, drop out, enroll again, and so on)
- date(s) on which they were certified (they may have qualified for Software Carpentry and Data Carpentry at different times)
- the date on which they taught their first workshop (if any)
"Mean time to teach first workshop" isn't a good metric, since roughly 1/3 of the people we've trained haven't taught yet. Should we use an inverted half-life measure, i.e., how long until the odds of someone having taught hit 50%? Or would something else give us more insight? Whatever we choose needs to be robust in the face of a big spike in our data in January 2016, when we retroactively certified a big batch of Data Carpentry instructors. If you have suggestions, comments on this post would be very welcome.
This post originally appeared in the Software Carpentry blog.