Webcraft Assessment
2 December 10 (holy cow, its december?!)
Attendees:
Agenda
- Brief overview of current plan for SoW January courses
- Current thoughts on assessments
- Discuss
Goals
- Bring in key assessment folks (you!) 'early' in the game to get ideas and direction
- Gut check on approach and assumptions
- Get some answers to some of the open questions
---------
<framing>
January SoW courses:
Goals:
- Start small enough to manage and thoughtfully think through, but want to learn as much as possible to ramp up quickly
- Try out assessment in this open environment (reactions, adoption, etc), potentially get the community excited about assessment/badges
- Have some success stories (if they exist) (examples of a badge getting someone hired, case studies, etc)
- Have some failure stories (recognize where things didn't work and adapt)
Skills:
- 2 skills defined by us:
- javascript (hard skill)
- accessibility (softer skill)
- Suggestions from the community (you, webcraft community, moz evangelists, etc)
Assessments:
- like the concept of challenges (especially for js) - not overly defined or constrained so people can do personally relevant work or submit existing work (tie in with Harvesting Gradebook idea)
- plan is to define the rubric - already working with webcraft community, Pippa and others to drill down and define the core elements (see David Bruant's js breakdown here: http://pad.p2pu.org/webcraft
- then potentially allow the peer community to assess and determine if the badge should be issued?
- we feel it is important to have peers involved, but how to manage this is an open question
Other:
- Community participation badges - through Stack Overflow type forum environment - awarded automatically by the system
- Should we do this in the pilot as well or will that dilute the system too quickly?
</framing>
<discussion>
Webcraft Assessment
2 December 10 (holy cow, its december?!)
Attendees:
Alex
Nils
Erin
22/11/10
JavaScript Challenges from Wikiversity
http://en.wikiversity.org/wiki/JavaScript_Challenges
Thanks to Michael Nelson.
-------------------------------------------------------------
19/11/10
Agenda
- Joshua to report back on progress
- roadmap for implementation
- 24 Nov - P2PU Call
- 25 Nov - Webcraft Call /
- 26 Nov - OSQA capabilities reported [JG]
- 3 Dec - Final decision on which competencies we want to give badges for - community feedback and desired competencies to Erin, Alex etc [PB]
- 17 Dec - Mechanics first draft of assessment for these skill [EK]
- 17 Dec - 31 Dec: Get feedback on assessment draft from assessment crowd, like Nils, Theron, Alex, Ahrash,Ahrash, etc...
- 31 Dec 2011 - Identify courses to add assessments to. [PB]
- 26 Jan 2011 - courses start
- early March 2011 - Surveys to assessment participants, to peer responders, related courses
- How specifically linked to courses are the assessments / should they be?
- Roles of the people involved (Erin, Pippa, Josh, Philipp, Paul/Dan, etc.)
- Potential Webcraft Assessments for January
- What hard / soft skills are we going to assess? [Pippa + Webcraft community]
- How are we assessing them [Erin + Josh]
- How specifically linked to courses are the assessments / should they be?
- P2PU Assessment Working Group - how does this project report back to P2PU - who else can we invite to this group?
4 Parts to the Assessment and Badging
Infrastructure - Paul, Dan, Josh, (Robert Chang)
Badge Design - XML Schema generic / guidelines - Not sure who owns this (Robert Chang)
What are the skills we will assess for web developers? - Pippa, Philipp, Erin, Josh, Mozilla experts
Assessment - Erin
Which skills to assess (and start with)
Pippa to lead push to define skills for web developers (Mozilla, OWEA, Webcraft )
- Which ones to start with?
- "if its boring, maybe its not a good badge"??
- Using skills map as the foundation
- Feedback from Toolshed: biggest response around soft skills,
- HTML/CSS (front-end, basic, general) ... but ... not very sexy ;-)
- JavaScript (specific, technical, but also broadly relevant)
- How to assess this, is not clear yet - what does it mean to know js? what are the learning goals? the levels?
- Also, processing.js 1.0 was just released that has parity with the Processing language ... it is a language designed for being accessible to artists and designers ... not as technically difficult to learn, yet powerful and useful.
- DOM Scripting Course from WaSP Interact:
- Exam Questions: http://interact.webstandards.org/curriculum/front-end-development/dom-scripting-1?exam
- Assessments: http://interact.webstandards.org/curriculum/front-end-development/dom-scripting-1?assign
- How would this translate into a badge - what would that badge represent?
- Are there leveled badges (foundations, js2, etc)
- Embed learning hard skills in interesting learning contexts (courses not on "learning JavaScript" but on "building cool web-sites" and you learn JavaScript as a part of that)
- Accessibility
- What does this mean? How do you "measure" accessibility?
- requires element of reflection, perhaps make a video of their thoughts or perspectives on accessibility?
- Soft skills? Hackers habits?
- Ability to work in a group
- Ability to plan
- Explaining technical concepts
- Feedback from Toolshed: Need explanation around the soft skills we had previously discussed. For example, "ability to answer questions" should be placed within the context of working as a web developer - to show /why/ that is an important skill.
- Assessments are independent of individual courses? (there might be multiple courses on js, but one assessment/badge about js)
- need to spend more time to figure out how/if this could work
How to assess them
Erin to lead efforts to define how to assess the skills within the Webcraft social learning environment
- Relationship between use of portfolios and badges
- Consider the audience (Internal to other web developers, externally to employer
- Well written assessments can help people understand what they still need to learn or to seek out
- Need to capitalize on the social learning that is occuring within these courses/this community - that should be built in and/or reflected in the assessment
Separating Courses and Assessment
Identify courses that would be relevant for badges and put it in.
What are the skills that are important?
Answer comes from Mozilla and OWEA
what do they feel are important - what do they feel are important to employers
what does it mean to know Javascript?
there's a process / a rubric
strawmen / push models
use the WaSP competencies as the model to ask for review on:
once we know the competencies
then we break them down (bring alex & erin to lead)
To Talk About Later:
separating courses and assessments
plagiarism challenges with peer assessment
how do we track
22/11/10
JavaScript Challenges from Wikiversity
http://en.wikiversity.org/wiki/JavaScript_Challenges
Thanks to Michael Nelson.
-------------------------------------------------------------
19/11/10
Agenda
- Joshua to report back on progress
- roadmap for implementation
- 24 Nov - P2PU Call
- 25 Nov - Webcraft Call /
- 26 Nov - OSQA capabilities reported [JG]
- 3 Dec - Final decision on which competencies we want to give badges for - community feedback and desired competencies to Erin, Alex etc [PB]
- 17 Dec - Mechanics first draft of assessment for these skill [EK]
- 17 Dec - 31 Dec: Get feedback on assessment draft from assessment crowd, like Nils, Theron, Alex, Ahrash,Ahrash, etc...
- 31 Dec 2011 - Identify courses to add assessments to. [PB]
- 26 Jan 2011 - courses start
- early March 2011 - Surveys to assessment participants, to peer responders, related courses
- How specifically linked to courses are the assessments / should they be?
- Roles of the people involved (Erin, Pippa, Josh, Philipp, Paul/Dan, etc.)
- Potential Webcraft Assessments for January
- What hard / soft skills are we going to assess? [Pippa + Webcraft community]
- How are we assessing them [Erin + Josh]
- How specifically linked to courses are the assessments / should they be?
- P2PU Assessment Working Group - how does this project report back to P2PU - who else can we invite to this group?
4 Parts to the Assessment and Badging
Infrastructure - Paul, Dan, Josh, (Robert Chang)
Badge Design - XML Schema generic / guidelines - Not sure who owns this (Robert Chang)
What are the skills we will assess for web developers? - Pippa, Philipp, Erin, Josh, Mozilla experts
Assessment - Erin
Which skills to assess (and start with)
Pippa to lead push to define skills for web developers (Mozilla, OWEA, Webcraft )
- Which ones to start with?
- "if its boring, maybe its not a good badge"??
- Using skills map as the foundation
- Feedback from Toolshed: biggest response around soft skills,
- HTML/CSS (front-end, basic, general) ... but ... not very sexy ;-)
- JavaScript (specific, technical, but also broadly relevant)
- How to assess this, is not clear yet - what does it mean to know js? what are the learning goals? the levels?
- Also, processing.js 1.0 was just released that has parity with the Processing language ... it is a language designed for being accessible to artists and designers ... not as technically difficult to learn, yet powerful and useful.
- DOM Scripting Course from WaSP Interact:
- Exam Questions: http://interact.webstandards.org/curriculum/front-end-development/dom-scripting-1?exam
- Assessments: http://interact.webstandards.org/curriculum/front-end-development/dom-scripting-1?assign
- How would this translate into a badge - what would that badge represent?
- Are there leveled badges (foundations, js2, etc)
- Embed learning hard skills in interesting learning contexts (courses not on "learning JavaScript" but on "building cool web-sites" and you learn JavaScript as a part of that)
- Accessibility
- What does this mean? How do you "measure" accessibility?
- requires element of reflection, perhaps make a video of their thoughts or perspectives on accessibility?
- Soft skills? Hackers habits?
- Ability to work in a group
- Ability to plan
- Explaining technical concepts
- Feedback from Toolshed: Need explanation around the soft skills we had previously discussed. For example, "ability to answer questions" should be placed within the context of working as a web developer - to show /why/ that is an important skill.
- Assessments are independent of individual courses? (there might be multiple courses on js, but one assessment/badge about js)
- need to spend more time to figure out how/if this could work
How to assess them
Erin to lead efforts to define how to assess the skills within the Webcraft social learning environment
- Relationship between use of portfolios and badges
- Consider the audience (Internal to other web developers, externally to employer
- Well written assessments can help people understand what they still need to learn or to seek out
- Need to capitalize on the social learning that is occuring within these courses/this community - that should be built in and/or reflected in the assessment
Separating Courses and Assessment
Identify courses that would be relevant for badges and put it in.
What are the skills that are important?
Answer comes from Mozilla and OWEA
what do they feel are important - what do they feel are important to employers
what does it mean to know Javascript?
there's a process / a rubric
strawmen / push models
use the WaSP competencies as the model to ask for review on:
once we know the competencies
then we break them down (bring alex & erin to lead)
To Talk About Later:
separating courses and assessments
plagiarism challenges with peer assessment
how do we track