Mozilla Open Badges 201
Badge System Design & Technology Review

Megan Cole
Marketing Lead
megan@mozillafoundation.org
@me...
Welcome to our 201 Webinar
Badge System Design Overview
Technical Overview
7 Steps for Roadmapping
What’s Next
And more...
A

differing opinions

Assessment Assessment
Assessment
Assessment Assessment Assessment
Assessment Assessment
Assessment
B

Some folks say our educational system is…
C

many challenges
seat time
complicated metrics
overcrowding
remediation
Badges act as representations of
achievements, learning, skills,
interests, competencies
hard & soft skills,
peer assessment, and
stackable lifelong learning
Open Badges are a form of
personal social currency
you can share across the web
How are we getting there?
Through a
shared infrastructure:
a universal standard
Badge metadata spec
+ Issuer API
(and in 2014 an Endorser API)
Badge name
Badge URL (description)
Badge criteria
Badge image
Issuer
Issue date
Recipient
Alignment (standards)
Expiration...
What does this mean
in practice?
formal & informal
learning pathways
Can I see an example?
Badge System Design
http://bit.ly/badgesystemdesign
http://bit.ly/badgesystemdesign

1. Badge Team

2. Badge Info

3. Badge Tech

4. Badge Design
http://www.digitalme.co.uk/badgecanvas/
Homework
exercise #1: write down your
top 3 badge system goals
(5 minutes)
Homework
exercise #2: copy the
spreadsheet & begin working
through your first badge
(7 minutes)
Homework
exercise #3: share your badge
thinking with us at
badges@mozillafoundation.org
(8 minutes)
http://bit.ly/BSDwiki
http://bit.ly/ob-research
Technology Overview
Mozilla’s  Open  Badge  Infrastructure
Free and open source software Backpacks and APIs
http://community.openbadges.org/
http://bit.ly/OB_IssuerAPI

API: An application programming interface (API) that specifies how software
components should i...
http://bit.ly/OBWidgets

Widget: A small application with limited functionality that can be installed and
executed within ...
http://bit.ly/platform-chart
http://bit.ly/OBIDev
7 key points in roadmapping
and resource management
1. Funding
2. Partnerships
3. Research
4. Badge system design
5. Time management
6. Technical resources
7. Design resource...
1. Funding
How might you actively think
about the personnel and
required resources needed to
build your best possible badge
system?
2. Partnerships
How might you freely imagine
the system that you might be
able to build with others?
3. Research
How might you intentionally
plan for the ways that badges
may influence you & your
teams as well as your badge
earners?
4. Badge System
How might you consciously
think about the genealogy of
your system and it’s future
growth?
5. Timing
How might you deliberately
plan for a full system life cycle?
6. Technology Resources
How might you best architect
your team to fail fast and
maximize success?
7. Design Resources
How might you dynamically
explore the most compelling
visual representation of your
system?
1. Funding
2. Partnerships
3. Research
4. Badge system design
5. Time management
6. Technical resources
7. Design resource...
What’s Next?
Stay in Touch
Join our weekly Community call
Wednesdays at 9am PDT / 12pm EDT
http://bit.ly/OBCommCalls
Post questions to ...
THANK YOU!

http://openbadges.org || @OpenBadges
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Mozilla Open Badges 201
Upcoming SlideShare
Loading in …5
×

Mozilla Open Badges 201

1,783 views

Published on

Slides from @megcolek
Mozilla Open Badges 201 Webinar, Nov. 13, 2013

Published in: Education, Technology

Mozilla Open Badges 201

  1. 1. Mozilla Open Badges 201 Badge System Design & Technology Review Megan Cole Marketing Lead megan@mozillafoundation.org @megcolek Sunny Lee Product Lead sunny@mozillafoundation.org @soletelee This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
  2. 2. Welcome to our 201 Webinar Badge System Design Overview Technical Overview 7 Steps for Roadmapping What’s Next And more...
  3. 3. A differing opinions Assessment Assessment Assessment Assessment Assessment Assessment Assessment Assessment Assessment
  4. 4. B Some folks say our educational system is…
  5. 5. C many challenges seat time complicated metrics overcrowding remediation
  6. 6. Badges act as representations of achievements, learning, skills, interests, competencies
  7. 7. hard & soft skills, peer assessment, and stackable lifelong learning
  8. 8. Open Badges are a form of personal social currency you can share across the web
  9. 9. How are we getting there?
  10. 10. Through a shared infrastructure: a universal standard
  11. 11. Badge metadata spec + Issuer API (and in 2014 an Endorser API)
  12. 12. Badge name Badge URL (description) Badge criteria Badge image Issuer Issue date Recipient Alignment (standards) Expiration date Evidence URL
  13. 13. What does this mean in practice?
  14. 14. formal & informal learning pathways
  15. 15. Can I see an example?
  16. 16. Badge System Design
  17. 17. http://bit.ly/badgesystemdesign
  18. 18. http://bit.ly/badgesystemdesign 1. Badge Team 2. Badge Info 3. Badge Tech 4. Badge Design
  19. 19. http://www.digitalme.co.uk/badgecanvas/
  20. 20. Homework exercise #1: write down your top 3 badge system goals (5 minutes)
  21. 21. Homework exercise #2: copy the spreadsheet & begin working through your first badge (7 minutes)
  22. 22. Homework exercise #3: share your badge thinking with us at badges@mozillafoundation.org (8 minutes)
  23. 23. http://bit.ly/BSDwiki
  24. 24. http://bit.ly/ob-research
  25. 25. Technology Overview
  26. 26. Mozilla’s  Open  Badge  Infrastructure
  27. 27. Free and open source software Backpacks and APIs
  28. 28. http://community.openbadges.org/
  29. 29. http://bit.ly/OB_IssuerAPI API: An application programming interface (API) that specifies how software components should interact with each other.
  30. 30. http://bit.ly/OBWidgets Widget: A small application with limited functionality that can be installed and executed within a web page by an end user.
  31. 31. http://bit.ly/platform-chart
  32. 32. http://bit.ly/OBIDev
  33. 33. 7 key points in roadmapping and resource management
  34. 34. 1. Funding 2. Partnerships 3. Research 4. Badge system design 5. Time management 6. Technical resources 7. Design resources
  35. 35. 1. Funding
  36. 36. How might you actively think about the personnel and required resources needed to build your best possible badge system?
  37. 37. 2. Partnerships
  38. 38. How might you freely imagine the system that you might be able to build with others?
  39. 39. 3. Research
  40. 40. How might you intentionally plan for the ways that badges may influence you & your teams as well as your badge earners?
  41. 41. 4. Badge System
  42. 42. How might you consciously think about the genealogy of your system and it’s future growth?
  43. 43. 5. Timing
  44. 44. How might you deliberately plan for a full system life cycle?
  45. 45. 6. Technology Resources
  46. 46. How might you best architect your team to fail fast and maximize success?
  47. 47. 7. Design Resources
  48. 48. How might you dynamically explore the most compelling visual representation of your system?
  49. 49. 1. Funding 2. Partnerships 3. Research 4. Badge system design 5. Time management 6. Technical resources 7. Design resources
  50. 50. What’s Next?
  51. 51. Stay in Touch Join our weekly Community call Wednesdays at 9am PDT / 12pm EDT http://bit.ly/OBCommCalls Post questions to our Google Group https://groups.google.com/d/forum/openbadges Stay up-to-date with our Blog http://openbadges.tumblr.com/ Reach out to us for information badges@mozillafoundation.org
  52. 52. THANK YOU! http://openbadges.org || @OpenBadges

×