1 / 14

Behind the Badge: Supporting robust co-curricular competency tracking programs

Explore the meaning and significance of competencies, artifacts, and experiences behind the badges in robust co-curricular competency tracking programs. Learn about a model for thinking about competencies and how to implement such a program on a campus. Discover a user achievement tracking system that connects to portfolios, supports multiple programs, and provides a roadmap to success.

cleor
Download Presentation

Behind the Badge: Supporting robust co-curricular competency tracking programs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Behind the Badge: Supporting robust co-curricular competency trackingprograms Scott Schopieray, Ph.D. Daniel Trego, MA College of Arts and Letters

  2. Too often we focus on the visual signifier (e.g. the Badge) in a credentialing program. But what does it mean to look behind that badge? What do we know about the competencies, artifacts, and experiences that a student who receives a badge has?

  3. Model for thinking about competencies

  4. Competency • Competencies are knowledge into action • Competencies are often comprised of sub-competencies and objectives

  5. Experience • Experience is student decided • Advising to ensure connections are made • Experience helps to develop artifacts

  6. Artifacts • Artifacts are evidence of learning or understanding • Artifacts can be cross-media, and often involve a reflective piece • Sum is greater than the parts

  7. So how do we implement this model on a campus with a real program?

  8. Overall Structure of Program • Develop competencies • Determine pathways of experience • Track/approve artifacts • Issue Credentials

  9. Technical Structure/Workflow • Portfolio {after experiences artifacts are displayed and stored} • User Achievement Tracking {show/organize/approve what students have done} • Credential Issuing {grant a credential} • Backpack {store/access credential}

  10. Our Project: User Achievement Tracking • User entered data • Faculty/advisor confirmation • Connected to portfolio (e.g. easy export) • Contains achievement info and reflection/evidence • Customizable based on program • Able to support multiple programs per student • Shows roadmap to program

  11. Questions? College of Arts and Letters Academic and Research Technology Scott Schopieray, Assistant Dean schopie1@msu.edu | @schopie1 Daniel Trego, Digital Media Specialisttregodan@msu.edu

More Related