- Our next meeting will be Monday, May 10th, 3PM Eastern time (US)
- Come up with an agenda for next week's meeting. Also, Ryan needs more experience moderating meetings on IRC.
- Interested parties should use a wiki page to collaborate on a list of possible Jobs or Roles. See below.
Job Task Analysis, or a step to Develop A CurriculUM (DACUM)
Before we can actually start creating any sort of a Curriculum, Syllabus, Learning Outcomes, Proficiency Standards, Competencies, or any of that, we need to come up with a list of Jobs one might be trained to do that are related to planning, implementing and maintaining a Drupal site. The idea here is to collect these roles and then create a face-to-face event where we try to collect all of the Job Tasks someone with each job description might have to know how to do.
After we get a list of Jobs or Roles, we will be holding a session around just ONE of these, e.g. Drupal Themer - what are all the things a themer needs to know? Once we have an understanding, we will open source that part.
After the Job Task Analysis, I understand there is a standard list of "Skills and Abilities" that can be mapped to almost any of these Tasks.
Once we know the Skills and Abilities we're aiming for, this part of the plan can be considered complete, and we can work on another Job or Role. If anyone wants to use the information we've created, that's another plan and another group. To think of it in another way, this is like a requirements gathering process, or the part where we make user stories, etc.
I'm sure I'm missing parts of this, but this is just to get a general gist of what the end point is.
Apparently what we're embarking on is a process of Instructional Design. The exact method is possibly yet to be determined. I am reaching out to someone whom I know has hard-core experience here, and I know some people in this group fall into that bucket as well.
The transcript from last week's chat is here: http://www.disobey.com/bot/log/drupal-dojo/2010-05-03#T3627789