Difference between revisions of "Documentation:Learning Environment"

From Kumu Wiki - TRU
Jump to navigation Jump to search
Line 132: Line 132:
| style="color:#000;padding: 2px" | <div id="mp-tfp"> '''[[/What Do We Know?|What Do We Know (Or Think We Know)?]]'''  
| style="color:#000;padding: 2px" | <div id="mp-tfp"> '''[[/What Do We Know?|What Do We Know (Or Think We Know)?]]'''  
'''[[LMS: What Do We Need to Find Out?| What Do We Need to Find Out?]]'''  
'''[[/What Do We Need to Find Out?| What Do We Need to Find Out?]]'''  
'''[[LMS: What Do We Hope For?| What Do We Hope For?]]'''
'''[[/What Do We Hope For?| What Do We Hope For?]]'''
'''[[LMS: What do we Fear| What Do We Fear?]]'''  
'''[[/What do we Fear| What Do We Fear?]]'''  

Revision as of 13:53, 13 March 2015

Learning Environment Project Page
Dedicated to enhancing TRU's online learning and teaching environment.

Improving the learning and teaching experience includes consistency in the learning environment for our students and staff. Moodle has been determined to be the potential preferred institutional fit at this point as it is open source and already used on campus. We are currently in the information gathering stage and are starting from a values perspective and drilling down to required functionality to meet those values. Please add your comments, thoughts, opinions and suggestions to these pages to help us capture all possible requirements. If you want to say something but not in a public forum, please contact Tanya, Brian or Jacquey to have the conversation.

Goals & Objectives (Draft)

To develop a learning environment students and faculty love that is alignment with the TRU Academic Plan and:

  1. Is easy to use appropriate support when required
  2. Supports learning that is:
    1. Engaging and interactive
    2. Supported (technical end user support? or...)
    3. Open
    4. Applied
    5. Flexible
    6. Research and data-driven
  3. Is cost effective, sustainable and supports continuous improvement while encouraging back end efficiencies
  4. Is implemented using a process that supports the needs of staff and faculty through appropriate process development, training and ongoing support

In Progress



  • A small group from Production, Instructional Design, Program Delivery and the Centre for Student Engagement have started work on a model to help visualize the possibilities.

Information Gathering

  • OL Students
  • Open Learning Faculty Members
  • Information gathering sessions with small groups of OLFMs Complete
  • Present progress to date to all OLFMs during May workshop

Information Sharing

  • Working on a list of useful sessions is currently being developed
  • Please let us know of any sessions you would find useful

Coming Soon

Information Gathering

  • Campus Students
  • The Centre for Student Engagement has agreed to assist with contacting Students beginning in March
  • Faculty
  • Phase I of consultation with the following Faculties
  • Natural Resources, Sciences, Trades and Technology, and Social Work
  • Faculty Council meetings - Brian is working on being added to the upcoming agendas

Information Sharing


High Level Discussion Questions (click a link below)

Emerging Themese (click a link below)

End user Interface Developing a system easy for both students and faculty

Course Development and Delivery Process Processes, Information, Rules and People

Successful Learning Research & Data Driven, Supported, Engaged & Interactive, Open, Applied

Other Considerations Anything missed in the above categories

Vs. Themes

Based on the emerging themes there are a couple of debatable topics that appear to have emerged. Hoping you will state your arguments for one or the other and help keep the conversation going via a little healthy debate.

Open vs. Closed

Using familiar tools vs. Learning new (useful) tools

Interaction with others vs. Completely independent

Deadlines vs. No deadlines

Nose Dive to Thriving