This document provides answers to some common questions about the Mentorship Program, as well as some administration questions.
Please note that we're in the process of renaming the workshop program to “Mentorship Program”.
A simple analogy would be the “shop” classes taught in high school, where students decide on a certain project that they would like to complete. For example, learning how to build something, be it a table, bicycle, or car engine(!). The workshop would begin at X time, students would come in, work on their projects, and project status would be updated. Most projects would have a defined beginning and end.
As of 08/20/2007, Saturdays are the obvious choice. The interest form has a questionnaire asking the parents for suggestions for the day of week and time(s) that would be best.
The workshop proposal also states that if students are not present within 1/2 hour of a scheduled workshop, the workshop can be closed, and will resume on the following scheduled date.
No, each individual student will have their own projects. If we get enough students and instructors interested in a given project, we can arrange to have more than one student on a single project. If student(s) wish to use Byteworks facilities for something that doesn't require instructor attention, this would work as well (e.g. schoolwork).
Several pre-defined projects should be available, to guide instructors/students towards deciding on a project. There will be times when students have questions that are not immediately attended to. Students will learn to use time wisely by either researching their questions in the meantime, or working on other aspects of their projects until an instructor is available to answer questions or provide guidance.
Each student should have a well defined timeline for their project, in addition to an up to date status that is taken by the instructors. Using this method, a student's main instructor need not be present in order for the student to continue on their project.
One currently popular model for this type of instruction is called Project Based Learning. There is tons of information available to help in building project-based curricula.
Probably not basement :)
Is it the best use of BWorks' resources to have a workshop for only one student?
A workshop of one student would be fine. The most effective classes (unfortunately) are the makeup classes where one instructor for one or two students. For example, two Programming makeup classes were taught in succession in 90 minutes to individual students.
At the other extreme, can you provide a meaningful experience to a class of 20 students?
A workshop of 20 students for one subject would be difficult, and would definitely dilute the value of the workshop time. Additional workshops would definitely be a consideration in this case. However, keep in mind that if 20 students were interested in different subjects, that we could divide the instructors among the 20 students. This would give 6 students per instructor.
The Byteworks Workshop Interest form should provide information on attendance expectation. If we have concrete numbers for attendance, we might be able to recruit volunteers to assist these students. Some volunteers might be averse to a “class” scenario where they would have to present something. However, these same volunteers might be more comfortable with a workshop setting that's slower paced, and more one-on-one, especially with students who have expressed a distinct interest in the subject that the volunteer has expertise in.
Indefinitely.
Byteworks will have at least one volunteer present for each workshop. The workshop would be *less* of a burden on other instructors and volunteers because it's a workshop, not a formal class. It would be like the student/apprentice who monitors the high school computer room when other students are using it. Yes, the apprentice won't be able to answer as many questions or give instructions for that week, but hopefully, the students would be able to start where they left off the prior week. For students who are new to a workshop, other students could show them what they've learned so far.
That is, what metrics will you consider so that you know when to alter the program, expand the program, or fold the program?
The program will be folded when there's ZERO students interested. Success will be measured by having ONE student who's interested show up.
Report Cards and Progress Charts could be used to track students' progress through workshop projects. Each project would have some form of milestones. At the end of a particular workshop session, each student's status should be updated by an instructor. Status would include the milestones that were accomplished by the student, and the next milestone to be reached. This would provide a starting point for the student at the next workshop session they attend. Remember, attendance is not mandatory. If a student becomes disinterested in a particular project, this will be noted, and a new project can be chosen by the student. See project report card and project progress template.
Each student could have a resume, which they can update with their accomplishments. Correct grammar and punctuation will be required, as well as formatting/presentation. The resume would of course be electronic, and perhaps be publicly available on the Internet for the students to present to friends/family. Of course, privacy would need to be considered – perhaps just the students' e-mail address would be used to distinguish between students.
Students can bring their own computers, especially if they're attending the hardware workshop.
Byteworks computers would be the main source of machinery. For software workshop activities, this would limit the amount of configuration/tinkering that needs to be done in order to get a working development machine.
If they will be using computers in the classroom/shop, who will maintain them?
Perhaps students can learn how to maintain the computers. For example, if a particular computer breaks down, then students from the hardware workshop could use the broken computer to learn how to diagnose and fix the problem? In other cases, the Byteworks volunteers will maintain the computers.
No. Byteworks will decide a starting date based on these factors:
We should probably start with the following qualifications:
Depending on the popularity of the workshop, we could reduce the requirements for workshop attendance. However, it would defeat the purpose of the workshop if it was overwhelmed by people who have other venues for learning / using computers.
Parents/adults deserve special considerations, just due to the age factor. Several adults from prior classes have expressed interest in volunteering. If there's interest from adults in a workshop, these adults would be more qualified and likely to assist other students in future workshops. So we would have a growing community of trusted volunteers.
It will take time, but a workshop environment like this could help Bytworks get more volunteers using this kind of ongoing mentorship. As more people learn by using Byteworks, they would hopefully give back their experience by teaching/mentoring in the future.
The workshop would keep the lines of communication open between Byteworks and former students. Students could use Byteworks Internet access for non-entertainment purposes, and Byteworks would be able to see how they're doing and provide additional help or get them interested in learning more.
The hardware workshop should not be overlooked. Students often pay more attention when the hardware is demonstrated to them. The computer hardware or photography workshop could easily be the most popular workhsops.