Instructional Technology Lead (ITL) Activities

Brief

The instructional technology lead (ITL) role provides consulting and collaboration services to faculty interested in integrating novel maker-, hardware-, software-, and cloud-based learning experiences into their iSchool courses. Our emphasis is on constructivist approaches to student engagement. We will be collaborating with INFO IT and Facilities, DIT, external partners, and the upcoming embedded data maker space, to improve student learning outcomes.

ITL - Current Projects (3/13/24)

Summary Table

Project Link

Description

Next Steps

Status

Priority

Project Link

Description

Next Steps

Status

Priority

1

Spaces

 

 

 

 

2

https://umdischool.atlassian.net/wiki/spaces/AP/pages/2134147073

iSchool Commons “storefront, hub, garage, basement, barn” for networking, IoT, cybersecurity, robotics, ed tech, and electronics projects

  • collaborating with Jason Aston (occasional equipment loans)

  • collaborating with Evan Levy (INST 751)

Maker, hardware, software, cloud

  • finish $35k Qualcomm Gift spending (about $25 K remaining)

  • need to plan on how to support > 350 students per semester in 346 while any 2024-2025 construction is occurring

  • seek collaborators and a possible alternative to Dennis and Donal teaching it

  • find synergies with C3

 

1

3

4111 Pod

temporary electronics and maker space

buy-in from most stakeholders achieved (waiting on 1)

Hardware, Maker

  1. move everything out of common area and clean

  2. repurpose or purchase shelves, tables, LED work lights, bins

  3. populate the shelves

  4. host an informal soft launch to learn about the space

(right after Spring Break?)

 

1

4

https://umdischool.atlassian.net/wiki/spaces/AP/pages/2318204935

Build hands-on lab capability for equity for Shady Grove students

hardware, Maker

designate spaces (comparable to what are emerging at College Park)

designate budget

acquire equipment

deploy equipment

 

1

5

 

 

 

 

 

6

Courses

 

 

 

 

7

https://umdischool.atlassian.net/wiki/spaces/AP/pages/2133426186

successor course to 346

focus on AWS hands-on through AWS Academy (of which UMD is a “founding” member) Cloud Foundations 20-hour course and several reference books

submitted for numbering and catalog approval (approved?!)

“survival cloud skills”

cloud

  • Dennis Builds Template Course

  • Donal Prepares to teach first section

  • Look into scalability as we go

 

1

8

part of course sequence to recruit and prepare possible teachers from the iSchool population; will feed into 371

hardware, software, cloud

  • first section was taught this fall MW 9:30-10:15 AM H302J

hardware, software, Maker

  • need to develop more instructors for the course

  • Build Fall 2024 as a template course

  • reorganize teaching materials (especially robotics kits) and need storage and staging space

  • work out instructional team and lab

  • submit for permanent course number and catalog

 

1

9

part of C3 grant

kits are part of IoT lab

course design started

hardware, software, cloud

  • reconcile with existing 388 courses

  • propose to program committee Spring 2024

 

 

2

10

Explore either a module for 201; or a 1 unit prep course (perhaps async but required), or a 3-unit elective to give those who might be interested in networking and cybersecurity some early practical and fun exposure to elements of 346.

hardware, cloud

Socialize idea to program committee and whom else?

 

1

11

ongoing course improvement

Maker, hardware, software, cloud

  • made adjustments for fall, especially in the areas of use of IoT Lab, Packet Tracer, new textbooks, and new teaching model

  • moved to lecture/required in-person discussion (lab, activities) model

  • sustainably scaling the in-person lab experience to 350 students and ultimately 480 students per semester

  • incorporating Ra Pi 5 into lab curriculum

  • standardizing on Kurose and Ross textbook and ancillary materials

 

1

12

“Wireless for Information Scientists” - all things Wireless

Socialize

Research

 

3

13

predecessor course to upper-division and graduate cybersecurity policy-based courses

hardware, software, cloud, Maker

  • keep identifying tech platforms (local = RaPi with Kali Linux; cloud = Naval Postgraduate school free resources)

  • finish draft syllabus

  • present to committee in December

  • strategize on when/where to offer it first

 

3

14

ongoing course improvement

hardware, cloud

  • hope to offer in 2024-2025

 

3

15

proposed follow on to 346

hardware, cloud

various directions

 

3

16

new course idea

software

consider as 1 unit; as 100 level iSeries; as 200 level; “how will QC impact me”

course development in Summer 2024, proposal in fall 2024

hope to offer in Spring 2025

 

3

17

ongoing course improvement

  • incorporate Apollo board game

  • incorporate Spaceflight Simulator

  • improve hands-on activities with craft materials

  • improvements in the areas of hands-on model building, physics appendix, and group cognition

Maker, software

  • incorporate Miro as collaborative in-class workspace

  • incorporate lessons from ENES 200 (Engineering Ethics)

 

3

18

Communities

 

 

 

 

19

Dennis will teach a section of ENES 200 (Engineering, Ethics, and Humanity) in Fall 2024 to learn the pedagogies used there and hopeful inform INFO pedagogy

Dennis Prepares for ENES 200

Dennis Teaches ENES 200

Dennis presents on ENES 200 potential relevance to INFO

 

1

20

nucleate community of interest and hopefully practice around iSchool XR projects

hardware, software

  • Place orders thru Chris with visibility across interested parties

  • eventually rationalize acquisition strategy

 

3

21

technology enablement across courses

software, cloud

collection point for discussion starters

 

1

22

 

 

 

 

 

23

Others (see children display)

keeping track of what might become important

  • as time allows; buckets for ideation

3

24

 

 

 

 

 

d

d


Staff

Currently the ITL role is filled by Dennis Frezzo, dfrezzo@umd.edu, Senior Lecturer (teaching 346, 362, 639J, 154, 208Z, 347 and some new upcoming courses). Working with student volunteers, iSchool IT mentees, graduate ambassadors, graduate TAs, graders, AMPs and undergraduate TAs. Thanks to all the staff who make all of this possible.

Dennis at Home IoT teaching “Cockpit”

Instructional Technology Meetings - Questions/Notes

3/13/24:

  1. 4111 Pod: Who is getting Kathy Weaver’s Office? Can we move all common area stuff out, clean, and move in some shelves now? Who does it and how do I request?

  2. Equitable Access to 346 Lab Experience: We followed a 2:1 (INFO to gift) ratio, plus space and Dennis' labor, so far to build IoT lab in Hornbake. I don’t want to spend down the whole $35 K qualcomm gift on duplicates for ESG. Is there any funding at ESG?

  3. What’s the priority amongst 388Z, 365, new 348, 349, 201x, or something else Dennis can develop?

  4. What’s the group’s advise on s buying the Panic Games Playdate Consoles ($2500) from the IoT Lab gift?

2/12/24 and 2/13/24:

Following up on XR discussions

8/9/23:

  1. continue updating this space with proposals and progress until semester starts

  2. explore ways to make these pages collaborative for anyone in iSchool faculty

11/17/22:

  1. IoT Lab has supported all sections of 346 this semester. Used for various tours. Grant received; planning expenses. When can we spend against the grant?

  2. Dennis gave guest interview for 104 on the use of Miro, Figma, and TinkerCad; Miro shared with other 362 sections.

  3. Will move this Wiki, in Spring semester, to allow more collaborative access.

  4. Working on 347 proposal to present to December Undergrad Curriculum meeting. AWS Academy and AWS Cloud Quest game under evaluation in 346 Cloud Computing module.

  5. 208Z approved. First working robot in iSchool commons completed! Kits in ordering process.

  6. IoT Design 1-unit. No update - does this impact overload calculations? What will be the numbering system for these courses.

  7. Working on 365 - Ethical Hacking - rejuvenation - any materials existing at all.

  8. Investigating how IoT Lab servers might be used in other courses

  9. Investigate outreach to support people sharing their work in Confluence

 

9/20/22:

  1. IoT Lab - integrated into 346; testing various interactions; what does the iSchool want next?

  2. Model of ITL as collaborator: Impact on 362 (use of Miro); Impact on 104 (dialog and presentation of 3 tools - Miro, Figma, TinkerCad); working with Donal and David W.; 3 other initial conversations; what else would iSchool like?

  3. who is admin for confluence for granting permissions and is it OK to invite people into the space with edit rights?

  4. Re: 347 - should be done with evaluation of AWS and syllabus revisions in October - what do we do next? Goal for Spring?

  5. Re: 208Z - should be done with evaluation of Vex kits and syllabus draft in October - what do we do next? Goal for Spring?

  6. Is there a set of specifications for the grant-funded ($5000) 1-unit courses (IoT Design in my case; have the kits and the ideas)? An online collaboration space? Deadlines?

 

Campus Educational Technology Links

Edward St.-John Teaching and Learning Center

UMD Center for Science and Technology in Education (CSTE)

TLTC Overview August 2022