Updated 11.1.2021 - moved history with "what has been done" to another page, and 12.1. updates in general

Teacher needs of technology for their teaching and needs for support

2021: support model development, collaboration at SCI and Aalto level2022: follow-up analysis on situation; iteration of data collecting, goals and actions2023; reaching goals2024; setting new goals
CS department
  • EDIT together with CS IT provides
    • new faculty member onboarding for educational technology
    • TA onboarding for A+ and JupyterHub (was 8.1.2021)
    • regular A+ training available ("training calendar") for teachers, TA:s and summer interns
    • online support via Daily Garage (?), email (RT) and chat
    • other online training based on needs!
  • collect feedback on the Zulip chat pilot
  • postponed from autumn 2020: teacher interviews for collecting use cases for development projects (at least for course grading process!) maybe with SCI or with LES&ITS


  • research-based teaching and learning methods
  • teacher satisfaction rate (set goal) on the available technology for their teaching
together at SCI and Aalto levels
  • follow-up survey one year after corona start, ca April-May
    • optional: Aalto-level participation in national survey on use of technologies in teaching*
  • collaboration with LES and Aalto-IT based on autumn experiences and feedback
    • webinars on technologies used in teaching spring 2021

Technology support for teaching and learning in courses

2021 spring: A+ and JH development for short-term critical needs, setting A+ long-time goals2021 autumn: A+ and JH development for short-term and long-term goals2022: follow-up analysis on situation; iteration of data collecting, goals and actions2023; reaching goals2024; setting new goals
Online learning environments: A+ and JupyterHub
  • A+ and JupyterHub in production
  • A+ development based on Aplus roadmap
  • A+ LTI development (to replace Astra in MyCourses/Moodle)
  • A+ future direction decisions (architect): project plan and setting goals, also with Helsinki
  • Preparations for Sisu:
    • A+ API development
  • collaboration starts with Helsinki and continues with Tampere
  • A+ future: development based on decisions with Helsinki and Tampere
  • JupyterHub: implementation of grading interface to A+


  • joint CS-LMS development with other universities based on in-house needs
  • JupyterHub (or other server resources) as a general service for as well teaching as research needs (maintainance and support model still open)


  • Joint LMS for CS needs with other Finnish universities
  • development model with is in harmony with national level decisions and needs
  • local resources for development, maintenance and support based on needs, in collaboration with CS department, Aalto-IT and LES
  • scalable solutions to support massive courses
Summative assessment / exams
  • Development of A+ exams in Exam studios, based on needs
  • online and Exam studio exams based on remote teaching needs
  • pilots based on teacher needs
  • support for teachers
  • electronic exams: focus on alternatives available in any circumstances
  • (original plan pre-corona: no retakes on paper)
  • simple process and support for teachers using electronic exams

  • no paper exams except for special needs
  • assessment focus less on summative assessment methods and more on formative methods during the course
  • electronic examining methods available for supporting assessment of skills included in course intended learning objectives
Course chats
  • pilot 2 (not production yet): Zulip for all SCI departments, incl collecting feedback and UI development needs
  • finding additional solutions based on needs
  • Start rundown of Non-GDPR-compliant external tools
  • goal: Zulip in production at Aalto level (in collaboration with CS IT & ITS,LES)
  • additional pilots based on needs and available solutions
  • goal: GDPR-compliancy in course chats

Preventing plagiarism
  • piloting developed tools (Watermarks?) on additional courses
  • further development (JupyterHub A+ integration for autograding would support preventing plagiarism as well)
  • student and teacher training & sharing best practices
  • sharing best practices, taking pilots to wider use

  • possible additional systems adoption plan, including teacher encouragement, pilots and training
  • e.g. Peergrade at Aalto level spring 2021

Technology support for teaching administrative needs

2021 spring and summer: participation in Aalto-level planning and development, own A+ development to meet the needs2021 autumn: further development to reach the goals2022: follow-up analysis on situation; iteration of data collecting, goals and actions2023; reaching goals2024; setting new goals
  • spring
    • A+ API development to support Sisu & Salesforce needs in course enrolment and grading!
    • Salesforce as OSR follower → active participation in Aalto project and own implementation
  • summer
    • OSR-SF migration (if needed) (or, OSR available for history data)
  • goal 1.12.2021 (visible in Aalto-level plans):
    • Sisu A+ integration in use with all needed integrations for course start (auto-enrolment) and end (grades)
    • Salesforce as OSR follower in the grading need (from course points to course grade)
  • OSR rundown (summer 2022)
  • Salesforce as OSR follower in analytics


systems providing awareness of student progress for teachers and heads of study programmes

Technology support for life-wide learning needs

2021 spring:

A+ development to meet LWL needs

2021 autumn:

A+ development to meet LWL needs

2022: follow-up analysis on situation; iteration of data collecting, goals and actions2023; reaching goals2024; setting new goals
  • HAKA (and O365, eduGain, mpass?) login to A+
  • priority on course material visibility alternatives?


open online courses are integrated with degree education in meaningful ways, as well by the technology used as the teaching practices.